Files
mcp-wms-wiki/wiki/concepts/task.md
T
arthur 9ce6ae37be lint(standard): corrections completes mode standard
- Em dashes: 1712 remplaces par tirets simples (86 fichiers + _index.md,
  en-tete section Limagrain conserve)
- Checklists: 24 '- [ ]' -> '- ☐' (3 pages operations, plus de todos Obsidian)
- Ancres: 33 reparees (slugs GitHub + ancres HTML <a id> reconnues),
  1 reciblee (manuel de reten)
- related: tenseflow -> tense-flow, pie -> mechanical-elements,
  group.md retire (doublon shipping)
- Registre: compteur global 122 -> 131 pages
- Rapport racine _lint_report.md mis a jour (scan v2 + re-scan final: 0 anomalie)
- Aucun fichier limagrain/ modifie (cloisonnement)
2026-07-20 13:01:21 +02:00

13 KiB
Raw Blame History

title, type, sources, related, last_compiled
title type sources related last_compiled
Task concept
areas/tasks/index.md
areas/tasks/tasks.md
areas/tasks/automatic_tasks.md
areas/tasks/movements.md
areas/tasks/semiautomatic_tasks.md
areas/tasks/automatic_tasks_manual_warehouse.md
areas/tasks/picking_tasks_manual_warehouse.md
areas/tasks/ERP/counts/cor.md
concepts/location.md
concepts/container.md
concepts/stock.md
concepts/putaway.md
concepts/picking.md
concepts/shipping.md
concepts/replenishment.md
concepts/count.md
2026-04-10

Task

Overview

A task is the fundamental unit of guided work in Easy WMS. It represents a physical movement to be performed within the warehouse: moving a container or loose stock from a source location/station to a destination location/station. Tasks are how the WMS communicates to operators (or automated systems) exactly what physical action to perform and in what order.

Tasks abstract the complexity of warehouse routing: the system handles compound routes, work zone restrictions, and equipment capabilities automatically. An operator on an RFT simply receives a task and executes it; they don't need to know which intermediate stations are involved. The same model applies to automatic warehouses, where tasks drive the AS/RS, AGVs, and conveyors.

Every significant warehouse process generates tasks: putaway, picking, shipping, replenishment, counts, crossdocking, kitting, defragmentation, and more. A task is always associated with a process type and a task type, which together define the exact operation required and which operators/equipment can execute it.

Types

Classification: Process type × Task type

Easy WMS distinguishes process type (the business process this task belongs to) from task type (the physical operation the operator/machine performs). The same task type (e.g., "Picking") can appear under different process types (e.g., Picking, Kitting, Replenishment, Dekitting).

Process type Task type Description
Putaway Putaway Manual warehouse: deposit container or loose stock at storage location
Putaway Approach Automatic warehouse (Pick & Pass): move containers with putaway tasks in P&P sub-warehouses
Putaway Movement Extract empty containers to PS; extract non-empty containers to PS
Picking Picking Direct picking: RF/voice terminal (manual) or at picking conveyor (automatic)
Picking Negative picking Automatic warehouses only: negative pick at PK conveyor
Picking Approach Automatic warehouse (Pick & Pass): move containers with picking tasks
Picking Cut Cut-to-location: cut specified length from roll/coil; leave remainder at location
Picking CutSupply Move roll/coil to cutting station for controlled cutting
Crossdocking Shipping Move crossdocked stock to buffer location
Crossdocking Loading Move crossdocked stock directly to dock
Crossdocking Putaway Move crossdocked stock to warehouse storage location
Crossdocking Replenishment to buffer Replenish tense flow buffer from crossdocked stock
Count Location count Physical count of all stock in a location (manual warehouses)
Count Container count Physical count of a container's contents (manual and automatic)
Count Item count Physical count of a specific item across locations (manual and automatic)
Replenishment Container replenishment Move container to picking dedicated location (PDL); also for empty container stacking
Replenishment Stock replenishment Move loose stock to PDL
Replenishment Picking Replenishment between sub-warehouses (picking task variant)
Replenishment Shipping Replenishment between sub-warehouses (shipping task variant)
Shipping Shipping Move container to buffer, consolidation station, or packaging location
Shipping Loading Move container to dock for truck loading
Kitting Picking Pick kit component stock for assembly
Kitting Shipping Move container to kit assembly conveyor/station
Dekitting Picking Pick a kit for disassembly
Dekitting Shipping Move container to assembly station for disassembly
Movement Movement Generic moves: container/stock relocation, stacker management, PK picking, cart distribution, container reallocation
Reject Reject Container rejection to designated location
Defragmentation Movement Move stock/containers to consolidate and optimize space
Defragmentation Shipping Move defragmented stock toward shipping
Picking locations emptying Movement Empty dynamic picking locations
Production Production Manufacturing module: supply tasks for production lines

Automatic warehouse vs. manual warehouse tasks

In manual warehouses, tasks are executed by operators using RFTs, voice terminals, or workstations. The physical movement is performed by a human using forklifts or on foot.

In automatic warehouses, tasks are executed by automated systems (AS/RS, AGVs, conveyors). The object must always be a container (never loose stock directly, as stock needs a container to move through the automated system). Container tasks include precise X/Y coordinates within rack locations.

Lifecycle

[Process event occurs]
        ↓
   Task CREATED (pending movement generation)
        ↓
   PENDING - waiting for movement to be generated
        ↓
   GENERATED - movement created, no operator/machine assigned yet
        ↓
   IN PROCESS - currently being executed
        ↓
   FINISHED - task completed successfully

   (at any point from Generated or In Process)
        ↓
   CANCELED - task stopped by user action

Status transitions

Status Description
Pending Task created but movement not yet generated. System is calculating route or waiting for conditions.
Generated Movement(s) created and ready for execution. Appears in operator queues.
In Process Operator/equipment has started the task. Stock or container is being moved.
Finished Task completed. Stock/container is at destination location.
Canceled Task stopped. Container/stock remains where the operator reports leaving it.

Tasks and movements

The task defines from where to where (source station → destination station). The actual path may pass through multiple intermediate stations. Easy WMS decomposes the task into movements - each movement covers one segment (one station to the next).

Each segment has a configured manager (who/what executes it):

  • RF: human operator with radio frequency terminal
  • Galileo (or equivalent): automated system (AS/RS, conveyor controller)
  • Voice: voice-directed operator
  • Workstation: pick-to-light / workstation operator

Example: A task moves a container from Station A to Station B via C, D, and E:

  • A→C: Galileo (AS/RS)
  • C→D: RF (operator)
  • D→E: Galileo
  • E→B: RF (operator)

This creates 4 movements. Each completes before the next begins. The task is complete when the container reaches B.

Movement statuses: Pending → In Execution

Movement release (reset In Execution → Pending) is available for resolving incidents, especially in automatic warehouses.

Business rules

  • Cannot manually complete picking, counting, replenishment (stock replenishment type), kit assembly, or consolidation tasks. These must be completed through their respective processes.
  • Task assignment to user or equipment respects work zone restrictions - if the equipment cannot access the required work zone or aisle, the task will not be executable.
  • Equipment incompatibility: equipment that cannot transport the container type specified in the task is ineligible.
  • Priority drives task sequencing within a process queue (lower number = higher priority; values: Very Low, Low, Normal, High, Urgent).
  • Task cancellation: container stays where the operator reports it (user must indicate the location, including position for rack locations or depth for channel locations).
  • Equipment release: allowed only when task is in Generated state (processed quantity = 0, no containers moved).
  • Count tasks cannot have their equipment released.

Configuration

Task execution order

For manual warehouse RF execution, the priority ordering is:

Automatic tasks (general): Round number → Priority → Empty channel → Stackability → Distance (picking route) → Aisle side (right first) → Height (low to high) → Creation date

Picking tasks: Round number → Priority → Empty channel → Stackability → Picking route → Aisle side → Height → Creation date

Shipping tasks: Round number → Priority → Empty channel → Stackability → Distance → Creation date

Wave picking: Priority (of the wave/orders assigned) → Route path (right and left sides, low to high - no second rounds)

Order picking (RF): For task selection: assigned to user/equipment first → Priority → Release date. For task execution: same as automatic tasks.

Semi-automatic mode

Allows tasks to be initiated by reading a container or location with stock, rather than receiving an explicit task assignment. Available task types: shipping, replenishment, putaway, movement, rejection.

Flow:

  1. Operator reads container or location with loose stock
  2. WMS shows summary of the best pending task (location, item if stock task, task type, destination, container to load)
  3. Operator clicks Start → task assigned → enters standard task flow
  4. WMS may propose additional tasks en route to optimize movements

Transactions are generated by the underlying process (not by semi-automatic mode itself).

UI: "Semi-automatic mode" from the "Tasks" menu (RFT).

Interface

Function Hardware Menu path
Tasks management and monitoring PC Warehouse → Tasks
Movement management PC Control → Movements
Automatic task distribution PC Warehouse → Tasks
Semi-automatic mode RFT Tasks → Semi-automatic mode
Manual task execution RFT Tasks → (process-specific options)

Available operations from Tasks view (PC)

Operation Restrictions
Manual task end Not allowed for: picking, counting, stock replenishment, kit assembly, consolidation
Task cancellation Container stays at location reported by user
Assign task to user Respects work zone restrictions
Assign task to equipment Respects type/zone/aisle restrictions
Unassign user Only if task not yet in execution
Unassign equipment Only if task not yet in execution
Priority change Very Low / Low / Normal / High / Urgent
Equipment release Only if In Process with zero processed quantity and no moved containers; not for count tasks

Common errors

Symptom Cause Solution
Task stuck in Generated Assigned equipment offline or cannot access work zone Release equipment; reassign to available equipment or leave unassigned
Task created but not assignable Equipment type incompatible with container type in task Assign different equipment; check equipment container type configuration
Task cannot be manually completed Task type is picking, counting, stock replenishment, kit assembly, or consolidation Complete via the appropriate process screen (picking station, count screen, etc.)
Movement stuck In Execution Automatic system malfunction or communication failure Use Movement Release to reset to Pending; investigate automation incident
Canceled task - container not found Operator reported wrong location at cancellation Run a count or check Last Known Location; resolve via Lost & Found if needed
Task not generated after process trigger Work zone restriction prevents any available equipment from executing Check work zone configuration and available equipment
  • location - tasks always have a source and destination location; location type (rack, compact, etc.) determines coordinate precision in tasks
  • container - most automatic warehouse tasks move containers; task references container code and type
  • stock - stock tasks (picking, replenishment) specify item, quantity, and logistic attributes
  • putaway - putaway process generates Putaway tasks; PIE/MU/TRL/ALM stations trigger automatic task creation
  • picking - picking process generates Picking tasks; wave/group picking generates batches of tasks
  • shipping - shipping process generates Shipping and Loading tasks for consolidation and dock delivery
  • replenishment - replenishment generates Container replenishment or Stock replenishment tasks to PDLs
  • count - count processes generate Location count, Container count, or Item count tasks