Mecalux/mcp-wms-wiki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

lint(standard): corrections completes mode standard

Browse Source 
- 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)
This commit is contained in:
Arthur
2026-07-20 13:01:21 +02:00
parent 7496aafe64
commit 9ce6ae37be
88 changed files with 1769 additions and 1871 deletions
Download Patch File Download Diff File Expand all files Collapse all files
wiki/concepts/stations.md
+27 -27
View File
@@ -72,16 +72,16 @@ Easy WMS defines 37+ standard station types. Types are identified by a numeric c
| Code | Type | Name | Description |
|------|------|------|-------------|
| 0 | ALM | Warehouse | Set of storage locations (shelves, ground locations, any storage element). Not connected to TMS — no machine communication. Involved in: location (destination), extraction (source), transfer (source+destination). Can be configured to allow/deny inbounds or outbounds independently. |
| 0 | ALM | Warehouse | Set of storage locations (shelves, ground locations, any storage element). Not connected to TMS - no machine communication. Involved in: location (destination), extraction (source), transfer (source+destination). Can be configured to allow/deny inbounds or outbounds independently. |
### Inbound / Conveyor Stations (AS/RS)
| Code | Type | Name | Description |
|------|------|------|-------------|
| 3 | PIE | Pallet Check Unit | Dimensional + identification control of containers. TMS sends height, weight, status, and label data to Easy WMS. Easy WMS validates and routes: correct → warehouse; wrong → REAC/RECH. All stations with a gauge arch or scale must be configured as PIE. PIE events evaluate flags: 65536=correct, 256=barcode error, 512=recovered container, 1024/66560=correct+empty, 3=holes+studs, 4=overheight, 8–64=overhangs, 128=weight excess. |
| 9 | ME | Aisle Inbound Conveyor | Interchange point with AS/RS (TRASLO). Final optimization before container enters the machine. Checks stacker crane characteristics (number of extractors, conveyors). If container arrives at ME with both putaway and picking tasks, putaway is cancelled and container goes to picking. Final location decision point — refines but doesn't replace initial search. Required in all automatic warehouses with stacker cranes. |
| 10 | MS | Outbound Conveyor | AS/RS unload point — where the machine unloads an extracted container onto the conveyor. Not mandatory (in Galileo IV the location is freed at AS/RS loading), but recommended for additional control, ring saturation prevention, and movement statistics. Taskless containers (order cancelled) return to vault. |
| 11 | MU | Putaway Conveyor | Searches for a putaway location by applying configured strategies. Only acts on containers without tasks or containers whose destination task points to this station. Useful when PIE is far from the warehouse — PIE skips location search, MU refines it just before warehouse entry. If problem generating movement: movement generated with origin=destination, flagged "With conflict"; cleared when possible. |
| 9 | ME | Aisle Inbound Conveyor | Interchange point with AS/RS (TRASLO). Final optimization before container enters the machine. Checks stacker crane characteristics (number of extractors, conveyors). If container arrives at ME with both putaway and picking tasks, putaway is cancelled and container goes to picking. Final location decision point - refines but doesn't replace initial search. Required in all automatic warehouses with stacker cranes. |
| 10 | MS | Outbound Conveyor | AS/RS unload point - where the machine unloads an extracted container onto the conveyor. Not mandatory (in Galileo IV the location is freed at AS/RS loading), but recommended for additional control, ring saturation prevention, and movement statistics. Taskless containers (order cancelled) return to vault. |
| 11 | MU | Putaway Conveyor | Searches for a putaway location by applying configured strategies. Only acts on containers without tasks or containers whose destination task points to this station. Useful when PIE is far from the warehouse - PIE skips location search, MU refines it just before warehouse entry. If problem generating movement: movement generated with origin=destination, flagged "With conflict"; cleared when possible. |
| 13 | APL | Stacker / Unstacker | Handles stacking and unstacking operations for empty containers. |
| 14 | LANZ | Shuttle | Shuttle station for Pallet Shuttle operations. |
| 18 | PKE | PK Inbound Conveyor | Entry to the picking inbound conveyor. |
@@ -91,15 +91,15 @@ Easy WMS defines 37+ standard station types. Types are identified by a numeric c
| Code | Type | Name | Description |
|------|------|------|-------------|
| 1 | TRASLO | AS/RS | Automated Storage/Retrieval System — the crane or machine. Bidirectional: loads from ME (inbound), unloads into MS (outbound). Communication via protocol (Galileo IV supports loading event + location release simultaneously). |
| 1 | TRASLO | AS/RS | Automated Storage/Retrieval System - the crane or machine. Bidirectional: loads from ME (inbound), unloads into MS (outbound). Communication via protocol (Galileo IV supports loading event + location release simultaneously). |
### Picking Stations
| Code | Type | Name | Description |
|------|------|------|-------------|
| 2 | PK | Picking Conveyor | Managed from the "Picking" view. Operator is guided: what to pick, how much, where to put it. Supports multiple locations per station (multiple containers simultaneously). Operations: direct picking, container/item count, replenishments. Can have associated RECH reject station. Empty container removal requires location configured for empty container handling. |
| 4 | PS | Outbound Conveyor | Final point of automatic transport — container leaves the warehouse. Management cycle of Easy WMS ends here (no more tasks). May have a display panel showing operator where to carry the container. Location types: Dynamic (Easy WMS tracks container depth) or Automatic (Easy WMS knows only which container is on PS, not which follows). |
| 16 | MP | Preparation Zone | Zone for order preparation — used in semi-automatic picking operations. |
| 4 | PS | Outbound Conveyor | Final point of automatic transport - container leaves the warehouse. Management cycle of Easy WMS ends here (no more tasks). May have a display panel showing operator where to carry the container. Location types: Dynamic (Easy WMS tracks container depth) or Automatic (Easy WMS knows only which container is on PS, not which follows). |
| 16 | MP | Preparation Zone | Zone for order preparation - used in semi-automatic picking operations. |
| 17 | Consolidation | Consolidation Station | Consolidation station for grouping picked stock by shipping order. |
| 53 | PCS | Sequencing Control Point | Point where order sequencing is controlled in the transport flow. |
| 54 | PB | Proximity Buffer | Buffer near a picking station to temporarily hold containers. |
@@ -112,19 +112,19 @@ Easy WMS defines 37+ standard station types. Types are identified by a numeric c
| Code | Type | Name | Description |
|------|------|------|-------------|
| 5 | REAC | Reconditioning | Destination for containers that fail PIE validation but can be corrected and re-injected into the flow. |
| 7 | RECH | Rejects | Destination for definitively rejected containers — not reintegrable. |
| 20 | ET | Transit Station | Intermediate station inserted in routes to break task flow. Does not perform any WMS management — designed for flexibility and external system integration (robotic arm, labeling machine, vertical warehouse, etc.). For automatic locations: only one container at a time (new arrival sends previous to Lost & Found). For non-automatic (buffer) locations: multiple containers allowed. TMS must always report aisle=1 in station update. |
| 7 | RECH | Rejects | Destination for definitively rejected containers - not reintegrable. |
| 20 | ET | Transit Station | Intermediate station inserted in routes to break task flow. Does not perform any WMS management - designed for flexibility and external system integration (robotic arm, labeling machine, vertical warehouse, etc.). For automatic locations: only one container at a time (new arrival sends previous to Lost & Found). For non-automatic (buffer) locations: multiple containers allowed. TMS must always report aisle=1 in station update. |
| 21 | CME | Inbound Control Station | Control point for inbound conveyors. |
| 42 | RETENTION | Retention | Retention station — holds containers that require manual review or authorization before continuing their route. |
| 42 | RETENTION | Retention | Retention station - holds containers that require manual review or authorization before continuing their route. |
| 43 | DESK | Desk | Desk station for administrative or manual operations. |
| 55 | ECB | Empty Containers Buffer | Buffer specifically for empty containers waiting to be stacked or reused. |
| 58 | ETQ | Labeller | Labeling machine station — container passes through and is automatically labeled. |
| 58 | ETQ | Labeller | Labeling machine station - container passes through and is automatically labeled. |
### Dock & Stage Stations
| Code | Type | Name | Description |
|------|------|------|-------------|
| 33 | Stage | Stage (Shipping/Receiving) | Floor area for temporary stock storage, typically near docks. Receiving stages: for stock pending putaway. Shipping stages: for client containers awaiting truck load. One of each can be set as default. Locations are DockStage type — Easy WMS does not control exact container position. Capacity = 0 means unlimited. Cannot be used for putaway; cannot generate tasks from stage (only from warehouse-type locations). |
| 33 | Stage | Stage (Shipping/Receiving) | Floor area for temporary stock storage, typically near docks. Receiving stages: for stock pending putaway. Shipping stages: for client containers awaiting truck load. One of each can be set as default. Locations are DockStage type - Easy WMS does not control exact container position. Capacity = 0 means unlimited. Cannot be used for putaway; cannot generate tasks from stage (only from warehouse-type locations). |
| 33 | PKS | Packing Station | Packing station for packaging operations (shares type code 33 with Stage). |
| 34 | Dock | Dock | Point of receipt or shipping. Types: inbound dock, outbound dock, or combined. At least one must be configured. Locations are DockStage type. No exact position tracking. Route must exist (even indirect) from container location to dock for task generation. Multiple locations per dock supported. |
@@ -133,7 +133,7 @@ Easy WMS defines 37+ standard station types. Types are identified by a numeric c
| Code | Type | Name | Description |
|------|------|------|-------------|
| 38 | Kit | Kits Assembly | Station for assembling kit items. |
| 57 | CONVEYOR | Conveyor (eCommerce) | Conveyor station for eCommerce operations — container-based order consolidation. |
| 57 | CONVEYOR | Conveyor (eCommerce) | Conveyor station for eCommerce operations - container-based order consolidation. |
| 59 | VAS | VAS Conveyor | Conveyor station for executing Value Added Services. |
| 61 | Cutting | Cutting Station | Station where cutting stock is cut in integrated or delegated picking processes. Composed of a receiving stage and a shipping stage (configurable: 1 shared stage, 2 dedicated stages, or shared stages across multiple cutting stations). Can be locked via "Stations" view to prevent stock assignment. |
| 65 | AGV | AGV Station | AGV robot station. |
@@ -146,7 +146,7 @@ A single physical station can have more than one role, enabling context-sensitiv
**PIE with multiple roles:** A PIE station configured as a rejection or reconditioning station simultaneously. The workstation view updates to show the appropriate interface (PIE vs RECH/REAC) based on the container's task. Configuration: arrange both stations in EasyS, create PIE→RECH/REAC route, add RECH/REAC as Error Entity for PIE. Then assign role in SmartUI "Stations" view via "Assign new role".
**PK with multiple roles:** PK station acting also as a reject station. When a container is rejected at PIE, the target reject station is the PK that originally handled the container — enabling workload balance and operator accountability. No SmartUI role assignment needed. Configuration: arrange PK+RECH in EasyS, create route, add RECH as Error Entity for PK. Special case: if no dedicated reject station exists, PK itself can be the PIE's error entity.
**PK with multiple roles:** PK station acting also as a reject station. When a container is rejected at PIE, the target reject station is the PK that originally handled the container - enabling workload balance and operator accountability. No SmartUI role assignment needed. Configuration: arrange PK+RECH in EasyS, create route, add RECH as Error Entity for PK. Special case: if no dedicated reject station exists, PK itself can be the PIE's error entity.
## Station Code Translation (FR / ES / EN)
@@ -169,7 +169,7 @@ Mecalux teams work across three languages; the same station can appear in logs a
## Station Capacity Semantics (GALILEO view)
Station capacity has a **different meaning** on PK and PS than on other stations — this trips up Gateway log analysis.
Station capacity has a **different meaning** on PK and PS than on other stations - this trips up Gateway log analysis.
| Layer | Generic station (conveyor/TK) | PK and PS |
|-------|-------------------------------|-----------|
@@ -181,7 +181,7 @@ Worked example (PK): 1 physical slot + 4 in transit on intermediate conveyors +
## Route configuration in EasyS (robotics)
In robotics installations, **every** movement between automated stations requires a route in EasyS. A single task (e.g. `PIE → Miniload`) can generate **N movements** (4 is typical) — the WMS creates one task, the routing table allows each hop.
In robotics installations, **every** movement between automated stations requires a route in EasyS. A single task (e.g. `PIE → Miniload`) can generate **N movements** (4 is typical) - the WMS creates one task, the routing table allows each hop.
> If no path exists, EasyWMS creates a **reject task** toward the configured reject station.
@@ -195,7 +195,7 @@ EasyS route types (cross-reference with Manager table below):
| **Manual** | Operator action triggered by a WMS task |
| **Virtual** | Instantaneous automatic movement (e.g. output → consolidation) |
**Reject routes** (in red) are special: they give the **task destination** (not the movement destination). Different `IdentError` reasons can target different reject destinations — see [IdentErrorType](https://msscc.mecalux.com/documentation/Development/master/ES/apis/easywms/Domain/IdentErrorType.md).
**Reject routes** (in red) are special: they give the **task destination** (not the movement destination). Different `IdentError` reasons can target different reject destinations - see [IdentErrorType](https://msscc.mecalux.com/documentation/Development/master/ES/apis/easywms/Domain/IdentErrorType.md).
For the protocol layer and message exchange (Search / End / Event / station updates), see [GALILEO Integration](../architecture/galileo-integration.md). For bring-up and simulation, see [Galileo Simulation](../operations/galileo-simulation.md).
@@ -210,7 +210,7 @@ Easy WMS generates tasks based on configured routes. Before generating a task, i
1. That a route exists between source and destination.
2. That the route is **active** (all stations in route are not locked).
Exception: shipping full containers via dock — only checks that a route exists, not whether it's active.
Exception: shipping full containers via dock - only checks that a route exists, not whether it's active.
If the shortest active route is blocked, Easy WMS immediately tries an alternative route.
@@ -218,7 +218,7 @@ If the shortest active route is blocked, Easy WMS immediately tries an alternati
### Route Managers (Executors)
Each simple route requires a declared manager — the type of element that will execute tasks on that route:
Each simple route requires a declared manager - the type of element that will execute tasks on that route:
| Manager | Executor |
|---------|----------|
@@ -226,7 +226,7 @@ Each simple route requires a declared manager — the type of element that will
| Monorail | Monorail system |
| RF | Operator with RFT (radio frequency terminal) |
| Voice | Operator with voice terminal |
| Virtual | Automatic — task auto-completes when container arrives at source station, no physical action |
| Virtual | Automatic - task auto-completes when container arrives at source station, no physical action |
| PTL | Pick-to-Light system |
| External | External system (AGV, vertical warehouse, ERP, etc.) |
| APS3D Fleet Manager | APS3D cart system |
@@ -278,10 +278,10 @@ Docks and stages are created in **EasyS** (or **Warehouse Designer**), not in Sm
## Related
- [[location]] — Location types associated with each station (DockStage, buffer, conventional)
- [[task]] — Every movement is a task; tasks decompose into simple route movements
- [[warehouse-designer]] — Stations are created in EasyS/Warehouse Designer, transferred to SmartUI
- [[picking]] — PK, MP, Workzone, Decision, PKE, TenseFlow, Consolidation all support picking
- [[reception]] — Dock, Stage, PIE stations are central to receiving workflows
- [[shipping]] — Dock, Stage, PS, Consolidation stations support outbound flow
- [[putaway]] — PIE triggers location search; MU refines it closer to warehouse
- [[location]] - Location types associated with each station (DockStage, buffer, conventional)
- [[task]] - Every movement is a task; tasks decompose into simple route movements
- [[warehouse-designer]] - Stations are created in EasyS/Warehouse Designer, transferred to SmartUI
- [[picking]] - PK, MP, Workzone, Decision, PKE, TenseFlow, Consolidation all support picking
- [[reception]] - Dock, Stage, PIE stations are central to receiving workflows
- [[shipping]] - Dock, Stage, PS, Consolidation stations support outbound flow
- [[putaway]] - PIE triggers location search; MU refines it closer to warehouse