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/glossary.md
+56 -56
View File
@@ -1,5 +1,5 @@
---
title: "Glossary — EasyWMS / Mecalux"
title: "Glossary - EasyWMS / Mecalux"
type: glossary
sources:
- wiki/concepts/container.md
@@ -86,7 +86,7 @@ related:
last_compiled: "2026-04-17"
---
# Glossary — EasyWMS / Mecalux
# Glossary - EasyWMS / Mecalux
All terms specific to EasyWMS (by Mecalux), including product names, abbreviations, AD element names, ERP message codes, and field names. General WMS/logistics terms are included only when EasyWMS usage differs from industry standard.
@@ -109,8 +109,8 @@ Self-navigating forklift or carrier used in automatic warehouses. Communicates w
**AI (Application Identifier)**
GS1 prefix code embedded in a barcode to identify the type of data that follows. Examples: AI(00) = SSCC, AI(02) = GTIN, AI(10) = lot, AI(17) = expiry date.
**ALM station (Almacén — Storage)**
Station type used as a pure storage entry/exit point. Containers are deposited at ALM stations for AS/RS retrieval to racks. In the FR/EN translation matrix: ALM (ES) = MAG (FR) = AIS (EN). See [Mechanical Elements — Station codes](concepts/mechanical-elements.md#3-station-codes--fr--es--en-matrix).
**ALM station (Almacén - Storage)**
Station type used as a pure storage entry/exit point. Containers are deposited at ALM stations for AS/RS retrieval to racks. In the FR/EN translation matrix: ALM (ES) = MAG (FR) = AIS (EN). See [Mechanical Elements - Station codes](concepts/mechanical-elements.md#3-station-codes---fr--es--en-matrix).
**AP / APC / APR (Apilador de Paletas)**
Pallet stacker machines. **AP** = Empty Pallet Stacker, **APC** = Chain Pallet Stacker, **APR** = Roller Pallet Stacker. See [Mechanical Elements](concepts/mechanical-elements.md#1-machine--equipment-acronyms-es--en).
@@ -119,10 +119,10 @@ Pallet stacker machines. **AP** = Empty Pallet Stacker, **APC** = Chain Pallet S
Automatic Pallet Shuttle variant using supercapacitors (SUPERCAP) instead of batteries. Faster charge cycles, shorter standalone runtime. See [Mechanical Elements](concepts/mechanical-elements.md).
**ATC (Abatible Transportador de Cadenas)**
Lift-up gate Chain Conveyor — chain conveyor with a retractable gate for pedestrian passage. See [Mechanical Elements](concepts/mechanical-elements.md).
Lift-up gate Chain Conveyor - chain conveyor with a retractable gate for pedestrian passage. See [Mechanical Elements](concepts/mechanical-elements.md).
**Automatic Aisle**
EasyS station element representing a stacker crane (TK) or Miniload. Linked to a rack; all locations inside the rack are reachable only through this aisle. See [Galileo Simulation — §3.4](operations/galileo-simulation.md#34-automatic-aisle-tk--miniload).
EasyS station element representing a stacker crane (TK) or Miniload. Linked to a rack; all locations inside the rack are reachable only through this aisle. See [Galileo Simulation - §3.4](operations/galileo-simulation.md#34-automatic-aisle-tk--miniload).
**APS (Automated Pallet Shuttle)**
3D compact storage system managed by the APS3D module. Locations tagged as APS or APSFIFO. The Fleet Manager controller coordinates lifts, shuttles, and conveyors. See [APS3D](modules/aps3d.md).
@@ -175,13 +175,13 @@ Putaway strategy variant applied **before** standard location strategies, used f
A container whose stock is assigned to a specific shipping order. The `Is client LPN` flag is true. Client containers are created during picking and track the prepared stock from pick face to shipping dock. See [Container](concepts/container.md).
**Client stock**
Stock that is inside a client container — i.e., stock that has been prepared for a specific outbound order. Cannot be adjusted without first un-preparing the shipment.
Stock that is inside a client container - i.e., stock that has been prepared for a specific outbound order. Cannot be adjusted without first un-preparing the shipment.
**CMC (Container Movement Confirmation)**
Inbound ERP request message. Asks the WMS to move a container between locations. Generates a Manual Movement task. See [ERP Interface](concepts/erp-interface.md).
**CME station (Control Miniload Entrée)**
Control station at the entry of a Miniload/TK. If the downstream TE is full, CME recirculates the container to avoid collision. Must report a "route full" status (3) when saturated — see [Stations](concepts/stations.md#route-configuration-in-easys-robotics) and [Galileo Integration](architecture/galileo-integration.md).
Control station at the entry of a Miniload/TK. If the downstream TE is full, CME recirculates the container to avoid collision. Must report a "route full" status (3) when saturated - see [Stations](concepts/stations.md#route-configuration-in-easys-robotics) and [Galileo Integration](architecture/galileo-integration.md).
**Conclure (replenishment)**
French SmartUI label for the **Top-off / Particular Demand** replenishment strategy. Pre-brings stock based on reserved outbound orders on the picking locations. See [Replenishment](concepts/replenishment.md).
@@ -245,10 +245,10 @@ Automatic conveyor element that routes containers to different destinations base
Process of moving containers between locations to optimize space and picking efficiency. Two strategies: **rotation** (by ABC class) and **shipping** (pre-position for orders). Automatic warehouse only. See [Defragmentation](concepts/defragmentation.md).
**Division (location cart)**
A subdivision of a **Location cart** used for wave / group picking. Each division is identified and can be tied to a specific order or wave, so one cart holds several concurrent pickings without mixing stock. See [Picking](concepts/picking.md#location-carts-chariots-à-emplacement).
A subdivision of a **Location cart** used for wave / group picking. Each division is identified and can be tied to a specific order or wave, so one cart holds several concurrent pickings without mixing stock. See [Picking](concepts/picking.md#location-carts-chariots-à-emplacement-for-multi-order-picking).
**DirectTransfer**
Value of the `<SorType>` field in the `SOR(01|02)` shipping order message, used for inter-warehouse transfers. Closing the expedition at origin automatically generates an `ASO01` on destination, pre-creating the incoming ASN container. Deleting the container from SmartUI triggers `ASK01`. Both messages carry **no reference to the source shipping order**. See [Order Outbound](concepts/order-outbound.md#asn--directtransfer-flow) and [Reception](concepts/reception.md#directtransfer--inter-warehouse-asn-flow).
Value of the `<SorType>` field in the `SOR(01|02)` shipping order message, used for inter-warehouse transfers. Closing the expedition at origin automatically generates an `ASO01` on destination, pre-creating the incoming ASN container. Deleting the container from SmartUI triggers `ASK01`. Both messages carry **no reference to the source shipping order**. See [Order Outbound](concepts/order-outbound.md#asn---directtransfer-flow) and [Reception](concepts/reception.md#directtransfer---inter-warehouse-asn-flow).
**Delete_StockStatusJob_PR**
Background job. Automatically removes time-expired stock quality locks. Runs every 15 minutes by default. See [Quality Control](concepts/quality-control.md).
@@ -260,7 +260,7 @@ Multi-Carrier XML message used to **merge** (fuse) several outbound orders into
Entity combining a carrier + consignee for a shipment. Holds tracking number, delivery note, and carrier label. Created when a shipping order is packaged at a Multi-Carrier station. See [Multi-Carrier](modules/multi-carrier.md).
**Dialog (AD)**
An AD element type representing a multi-step operator flow — typically a wizard or guided process on the RF terminal or SmartUI. Examples: `ReceptionDialog`, `PickingDialog`, `CountDialog`. Each step is a form with specific validations. See [Application Dictionary](architecture/application-dictionary.md).
An AD element type representing a multi-step operator flow - typically a wizard or guided process on the RF terminal or SmartUI. Examples: `ReceptionDialog`, `PickingDialog`, `CountDialog`. Each step is a form with specific validations. See [Application Dictionary](architecture/application-dictionary.md).
**DOM (Distributed Order Management)**
EasyWMS module for multi-node warehouse networks. Orchestrates sales orders across nodes using a 5-stage engine (region → carrier → stock → capacity → strategies). See [DOM](modules/dom.md).
@@ -269,17 +269,17 @@ EasyWMS module for multi-node warehouse networks. Orchestrates sales orders acro
Inventory control process where count discrepancies or adjustments require a second approval by a supervisor/manager before being committed to stock. Controlled via item count profile and `DOUBLE_VALIDATION_ACTIVE` parameter. See [Stock Adjustment](concepts/stock-adjustment.md) and [Count](concepts/count.md).
**DeleteEmptyContainers**
Station/location parameter that decides what happens to empty supports. Robotics default for automated locations: **Not Delete**. Picking stations (PK) may use `Delete` or `Ask` when operators physically remove empty containers. See [Galileo Simulation — §3.1](operations/galileo-simulation.md#31-location--container-settings).
Station/location parameter that decides what happens to empty supports. Robotics default for automated locations: **Not Delete**. Picking stations (PK) may use `Delete` or `Ask` when operators physically remove empty containers. See [Galileo Simulation - §3.1](operations/galileo-simulation.md#31-location--container-settings).
**DTR (Document Technique de Référence)**
Reference document listing all technical elements for a robotics project (hardware, IPs, services, accounts) and the responsibility split between Mecalux and the client. Template on [Confluence](https://easywmsfrance.atlassian.net/wiki/spaces/EF/pages/3000562515980). See [Robotics Project Lifecycle — §2](operations/robotics-project-lifecycle.md#2-dtr--document-technique-de-référence).
Reference document listing all technical elements for a robotics project (hardware, IPs, services, accounts) and the responsibility split between Mecalux and the client. Template on [Confluence](https://easywmsfrance.atlassian.net/wiki/spaces/EF/pages/3000562515980). See [Robotics Project Lifecycle - §2](operations/robotics-project-lifecycle.md#2-dtr---document-technique-de-référence).
---
## E
**Exiger (replenishment)**
French SmartUI label for the **Dynamic / On-Demand** replenishment strategy — replenishment triggered when picking consumption empties a picking location, regardless of threshold. See [Replenishment](concepts/replenishment.md).
French SmartUI label for the **Dynamic / On-Demand** replenishment strategy - replenishment triggered when picking consumption empties a picking location, regardless of threshold. See [Replenishment](concepts/replenishment.md).
**Est renseigné (Count)**
SmartUI flag on a Count Order Line (`CountOrderLineVList`) that controls whether the line is **informed** (expected quantity visible to operator) or **blind** (hidden). Historical ERP sends it via COR `IsInformed`; SmartUI can toggle it per line afterwards. See [Count](concepts/count.md#blind-vs-informed-mode).
@@ -288,31 +288,31 @@ SmartUI flag on a Count Order Line (`CountOrderLineVList`) that controls whether
Barcode standard for item identification. EAN-13 is the most common; used on item labels and for carton identification. Related to GS1/GTIN standards. See [Labels](concepts/labels.md).
**EasyS**
Mecalux's layout configuration tool for EasyWMS, and **3D robotics simulator** that speaks the same protocol as GALILEO. Used to: (1) define physical warehouse topology — aisles, racks, locations, stations, equipment groups, routes; (2) run a full simulation with an EasyWMS Gateway for development and demos (port 3000, Start → Simulation 3D, PIE injection via PIE Info tab). Shared demo VM at Mecalux France: ALL on LYOITSW02 (`10.58.10.75`). See [Galileo Simulation](operations/galileo-simulation.md).
Mecalux's layout configuration tool for EasyWMS, and **3D robotics simulator** that speaks the same protocol as GALILEO. Used to: (1) define physical warehouse topology - aisles, racks, locations, stations, equipment groups, routes; (2) run a full simulation with an EasyWMS Gateway for development and demos (port 3000, Start → Simulation 3D, PIE injection via PIE Info tab). Shared demo VM at Mecalux France: ALL on LYOITSW02 (`10.58.10.75`). See [Galileo Simulation](operations/galileo-simulation.md).
**EasyWMS Gateway**
Windows service (`EasyWMSGateway2015`) that brokers all communication between EasyWMS and the automation layer (GALILEO in production, EasyS in simulation). Installed at `C:\Program Files\Mecalux\EasyWMS Gateway 2015`; config at `C:\ProgramData\Mecalux\EasyWMS Gateway 2015\Config\MainObject.config` (tenantCode + TokenUser); logs at `C:\ProgramData\Mecalux\EasyWMS Gateway 2015\Logs\AllLog.log`; uses TCP port 3000. See [Galileo Integration](architecture/galileo-integration.md).
**End (GALILEO message)**
GALILEO-to-WMS message that signals a movement has completed. Carries an `EndErrorCode` (0 = OK, 1 = deposit error, 2 = extraction error, 4 = inconsistent order — config mismatch, 7 = gauge error). Processed by `Galileo_EndCreatedEventHandler_PR`. See [Galileo Integration — End](architecture/galileo-integration.md#3-end-log--end0-end1-).
GALILEO-to-WMS message that signals a movement has completed. Carries an `EndErrorCode` (0 = OK, 1 = deposit error, 2 = extraction error, 4 = inconsistent order - config mismatch, 7 = gauge error). Processed by `Galileo_EndCreatedEventHandler_PR`. See [Galileo Integration - End](architecture/galileo-integration.md#3-end-log--end0-end1-).
**EndErrorCode**
Numeric code attached to a GALILEO End message. Value `4` is the most common diagnostic — indicates a configuration drift between EasyWMS and GALILEO (missing location, wrong allowed container type, X/Y out of range, impossible crossing). See [Galileo Troubleshooting — §3.1](operations/galileo-troubleshooting.md#31-enderrorcode--4-most-frequent).
Numeric code attached to a GALILEO End message. Value `4` is the most common diagnostic - indicates a configuration drift between EasyWMS and GALILEO (missing location, wrong allowed container type, X/Y out of range, impossible crossing). See [Galileo Troubleshooting - §3.1](operations/galileo-troubleshooting.md#31-enderrorcode--4-most-frequent).
**Empileur (EMP / APL)**
Pallet stacker station (code 13). See [Stations](concepts/stations.md) and [Mechanical Elements](concepts/mechanical-elements.md).
**EMS (Sistema electrovía aérea)**
Overhead Electric Monorail — suspended pallet transport system. See [Mechanical Elements](concepts/mechanical-elements.md).
Overhead Electric Monorail - suspended pallet transport system. See [Mechanical Elements](concepts/mechanical-elements.md).
**ECB (Empty Container Buffer)**
Station type 55 — buffer specifically for empty containers waiting to be stacked or reused. See [Stations](concepts/stations.md).
Station type 55 - buffer specifically for empty containers waiting to be stacked or reused. See [Stations](concepts/stations.md).
**Event (GALILEO message)**
GALILEO-to-WMS message declaring container presence at a checkpoint. Primary source is the PIE (barcode + gauge + weight). Content varies by station; flags `65536`=OK, `256`=barcode error, `512`=recovered, `1024`/`66560`=empty OK, `4`=overheight. Processed by `Galileo_PIEEventHandler_PR`. See [Galileo Integration — Event](architecture/galileo-integration.md#1-event-log--event).
GALILEO-to-WMS message declaring container presence at a checkpoint. Primary source is the PIE (barcode + gauge + weight). Content varies by station; flags `65536`=OK, `256`=barcode error, `512`=recovered, `1024`/`66560`=empty OK, `4`=overheight. Processed by `Galileo_PIEEventHandler_PR`. See [Galileo Integration - Event](architecture/galileo-integration.md#1-event-log--event).
**ETQ (Étiqueteuse)**
Labeller station type 58 — an automatic labelling machine through which a container passes to receive a printed label. See [Stations](concepts/stations.md).
Labeller station type 58 - an automatic labelling machine through which a container passes to receive a printed label. See [Stations](concepts/stations.md).
**eCommerce module**
EasyWMS add-on module for e-commerce fulfillment. JIT reception flow: single-unit orders go to packing, multi-unit to ungrouping, no-order stock to storage. See [eCommerce](modules/ecommerce.md).
@@ -326,7 +326,7 @@ In EasyWMS, an equipment is a physical device (forklift, hand truck, conveyor se
**ERP Interface**
The set of standardized messages exchanged between EasyWMS and the customer's ERP system (SAP, Oracle, etc.). Three-letter codes identify each message type (ROR, SOR, ASN, ROF, SOF, etc.). See [ERP Interface](concepts/erp-interface.md).
**ET station (Estación de Tránsito — Transit)**
**ET station (Estación de Tránsito - Transit)**
Station type used as an intermediate buffer between two zones that cannot directly route to each other. A conveyor element in EasyS; appears in the "Automatic elements" group. Required for multi-zone replenishment flows. See [Stations](concepts/stations.md).
**Event (AD)**
@@ -351,7 +351,7 @@ Shipping/storage logic where the oldest stock (by receipt date) is consumed firs
**Fleet Manager**
Controller software/hardware that coordinates APS3D shuttle movements, lifts, and conveyors. Communicates with EasyWMS via the Fleet Manager protocol. See [APS3D](modules/aps3d.md) and [Stations](concepts/stations.md).
**Fusion (order fusion) — synonym Merge**
**Fusion (order fusion) - synonym Merge**
Grouping of two or more shipping orders into a single picking wave for joint preparation. Orders in a fusion share picking tasks. See [Shipping](concepts/shipping.md).
---
@@ -362,10 +362,10 @@ Grouping of two or more shipping orders into a single picking wave for joint pre
Windows service provided by Mecalux that bridges Easy WMS workflows and the PostgreSQL exchange tables used by the AGV module. Serializes AGV tasks into `agv_outputqueue` / `agv_eag`, reads fleet manager responses from `agv_inputqueue` / `agv_age` / `agv_ags`. Polls at configurable intervals (default 1 second). Creates all PostgreSQL tables and sequences on first startup. Config file: `C:\ProgramData\Mecalux\EasyWMS GatewayAGV 2015\`. See [AGV](modules/agv.md) and [AGV Installation Guide](operations/agv-installation.md).
**Galileo**
Mecalux's production **Transport Management System (TMS)** — the automation layer that drives conveyors, stacker cranes (TK/Miniload), shuttles, AGVs and lifts. Has **no predictive vision**; only requests orders from EasyWMS and executes them. Also used inside EasyS as the label of the conveyor route type (opposed to Manual / Virtual) — a "Galileo" route is a physical hop that requires Gateway communication. See [Galileo Integration](architecture/galileo-integration.md) and [Stations](concepts/stations.md).
Mecalux's production **Transport Management System (TMS)** - the automation layer that drives conveyors, stacker cranes (TK/Miniload), shuttles, AGVs and lifts. Has **no predictive vision**; only requests orders from EasyWMS and executes them. Also used inside EasyS as the label of the conveyor route type (opposed to Manual / Virtual) - a "Galileo" route is a physical hop that requires Gateway communication. See [Galileo Integration](architecture/galileo-integration.md) and [Stations](concepts/stations.md).
**Galileo_PIEEventHandler_PR / Galileo_SearchCreatedEventHandler_PR / Galileo_EndCreatedEventHandler_PR**
The three core workflows consuming GALILEO messages: PIE events (inbound identification), Search requests (next-hop routing — can fire dozens per second, do not activate instance tracing carelessly), and End notifications (movement complete / error). See [Galileo Integration — AD entry points](architecture/galileo-integration.md#application-dictionary-entry-points).
The three core workflows consuming GALILEO messages: PIE events (inbound identification), Search requests (next-hop routing - can fire dozens per second, do not activate instance tracing carelessly), and End notifications (movement complete / error). See [Galileo Integration - AD entry points](architecture/galileo-integration.md#application-dictionary-entry-points).
**GalileoMovTrackingCreateCommand**
Preferred AD command for pushing a movement order to GALILEO (over the deprecated `GalileoMovTrackingCreateChangingTargetCommand`). Transition: movement `Generated` → `In progress`, container placed on virtual location **Mov**. See [Galileo Integration](architecture/galileo-integration.md).
@@ -393,10 +393,10 @@ Mecalux cobot integration protocol. The Cobot module connects robotic picking ar
Period immediately after MEP (go-live) during which the dev team handles bug fixes on the `develop` branch. Ends when the project is transferred to the Support team (TLM). See [Git Branch Lifecycle](operations/git-branch-lifecycle.md).
**IdentError / IdentErrorType**
Enum of rejection reason codes (PIE barcode unreadable, overheight, overhang, overweight, no ASN match…). Different IdentErrors can route containers to different reject destinations using **reject routes** (displayed in red in EasyS). Reference: [IdentErrorType doc](https://msscc.mecalux.com/documentation/Development/master/ES/apis/easywms/Domain/IdentErrorType.md). See [Galileo Simulation — §3.11](operations/galileo-simulation.md#311-reject-configuration).
Enum of rejection reason codes (PIE barcode unreadable, overheight, overhang, overweight, no ASN match…). Different IdentErrors can route containers to different reject destinations using **reject routes** (displayed in red in EasyS). Reference: [IdentErrorType doc](https://msscc.mecalux.com/documentation/Development/master/ES/apis/easywms/Domain/IdentErrorType.md). See [Galileo Simulation - §3.11](operations/galileo-simulation.md#311-reject-configuration).
**IMS (Sistema electrovía invertida)**
Inverted Electric Monorail — floor-based inverted monorail variant of EMS. See [Mechanical Elements](concepts/mechanical-elements.md).
Inverted Electric Monorail - floor-based inverted monorail variant of EMS. See [Mechanical Elements](concepts/mechanical-elements.md).
---
@@ -429,10 +429,10 @@ Performance metrics tracked in the Data Analytics module or displayed on the 3PL
## L
**Location cart (chariot à emplacement)**
Mobile cart divided into numbered **divisions**, used at the RFT for wave and group picking so a single operator prepares multiple orders in one pass without mixing stock. Requires specific SmartUI configuration (cart type, division count, assignment to work area). See [Picking](concepts/picking.md#location-carts-chariots-à-emplacement).
Mobile cart divided into numbered **divisions**, used at the RFT for wave and group picking so a single operator prepares multiple orders in one pass without mixing stock. Requires specific SmartUI configuration (cart type, division count, assignment to work area). See [Picking](concepts/picking.md#location-carts-chariots-à-emplacement-for-multi-order-picking).
**LogisticAttributeCreateLogisticCaptureCommand**
Run Command that adds a **capture mode** to an existing logistic attribute. Used with `CaptureMode = 2` and `CaptureProcess = 2` to create an attribute with **no capture mode** — that is, one auto-generated by custom code rather than prompted on the RFT/SmartUI. See [Product / Item](concepts/product-item.md#creating-a-logistic-attribute-without-a-capture-mode).
Run Command that adds a **capture mode** to an existing logistic attribute. Used with `CaptureMode = 2` and `CaptureProcess = 2` to create an attribute with **no capture mode** - that is, one auto-generated by custom code rather than prompted on the RFT/SmartUI. See [Product / Item](concepts/product-item.md#creating-a-logistic-attribute-without-a-capture-mode).
**LneTrmAlternative**
Sub-field of `<LneTerms>` in `SOR(01|02)`. Boolean flag enabling the **substitute item** feature at line level. When `true`, the WMS may ship the configured substitute items (see shipping profile mode: Partiel / Substitution / Tout ou rien) if the primary item has insufficient stock. Returned in `SOF` alongside `LneDIsAlternative` to flag the actual substitute used. See [Product / Item](concepts/product-item.md#alternative--substitute-items) and [Order Outbound](concepts/order-outbound.md#alternative-items-sor-flag--sof-feedback).
@@ -478,22 +478,22 @@ A stock or container relocation performed without generating a task. Eight move
Automatic warehouse station where containers exit the system onto multiple possible conveyor lanes. See [Stations](concepts/stations.md).
**ME / TE (Aisle Inbound Conveyor / Table d'entrée)**
Station type 9 — the conveyor at the entry of a TK/Miniload. Can hold multiple containers (layout uses Positions + Stack); configure `Logical X = 991` except for tables embedded in the rack. FR: TE, ES: ME, EN: Input Conveyor (IC). See [Stations](concepts/stations.md) and [Galileo Simulation — §3.8](operations/galileo-simulation.md#38-entry--outbound-tables-te--ts-on-the-tk).
Station type 9 - the conveyor at the entry of a TK/Miniload. Can hold multiple containers (layout uses Positions + Stack); configure `Logical X = 991` except for tables embedded in the rack. FR: TE, ES: ME, EN: Input Conveyor (IC). See [Stations](concepts/stations.md) and [Galileo Simulation - §3.8](operations/galileo-simulation.md#38-entry--outbound-tables-te--ts-on-the-tk).
**MS / TS (Outbound Conveyor / Table de sortie)**
Station type 10 — the outbound conveyor of a TK/Miniload. Shares the Positions + Stack configuration pattern with ME/TE. FR: TS, ES: MS, EN: Output Conveyor (OC). See [Stations](concepts/stations.md).
Station type 10 - the outbound conveyor of a TK/Miniload. Shares the Positions + Stack configuration pattern with ME/TE. FR: TS, ES: MS, EN: Output Conveyor (OC). See [Stations](concepts/stations.md).
**MP / TP (Preparation Zone / Table de préparation)**
Station type 16. Preparation tables linked to a picking station (PK) where operators deposit picked stock. Routes: **Manual** PK → MP, **Galileo** MP → outbound table, **Virtual** MP → consolidation. Assignment mode (Automatic / Manual) set via **Menu → Control → Workstations**. In manual mode, tasks do not generate until the outbound order is assigned to a table. See [Picking — PK/MP setup](concepts/picking.md#pk--mp-setup-and-assignment-mode).
Station type 16. Preparation tables linked to a picking station (PK) where operators deposit picked stock. Routes: **Manual** PK → MP, **Galileo** MP → outbound table, **Virtual** MP → consolidation. Assignment mode (Automatic / Manual) set via **Menu → Control → Workstations**. In manual mode, tasks do not generate until the outbound order is assigned to a table. See [Picking - PK/MP setup](concepts/picking.md#pk--mp-setup-and-assignment-mode).
**Miniload (ML / STL / TK)**
Light-load automated stacker crane used for bins/cases (typically ≤ 50–100 kg per load). Nomenclature: `ML` = Miniload, `B` (post-ML) = Bicolumn, `EPSF` = pelle simple fond (1 charge), `EPDF` = pelle double fond (1 charge, double-depth rack), `ECDF` = courroie double fond (2 charges). Each model drives the TE/TS table configuration in EasyS. See [Mechanical Elements — §4](concepts/mechanical-elements.md#4-miniload-nomenclature-tk--ml).
Light-load automated stacker crane used for bins/cases (typically ≤ 50–100 kg per load). Nomenclature: `ML` = Miniload, `B` (post-ML) = Bicolumn, `EPSF` = pelle simple fond (1 charge), `EPDF` = pelle double fond (1 charge, double-depth rack), `ECDF` = courroie double fond (2 charges). Each model drives the TE/TS table configuration in EasyS. See [Mechanical Elements - §4](concepts/mechanical-elements.md#4-miniload-nomenclature-tk--ml).
**Mov (virtual location)**
System virtual location that temporarily holds a container while it is physically travelling between two stations. Set on movement transition `Generated` → `In progress`; cleared on End with `EndErrorCode=0`. See [Galileo Integration — Task lifecycle](architecture/galileo-integration.md#tasks-vs-movements).
System virtual location that temporarily holds a container while it is physically travelling between two stations. Set on movement transition `Generated` → `In progress`; cleared on End with `EndErrorCode=0`. See [Galileo Integration - Task lifecycle](architecture/galileo-integration.md#tasks-vs-movements).
**Manual Action (EasyS)**
Test-mode checkbox on a picking station in EasyS. When ticked, the container **does not leave automatically** after picking confirmation — the operator must click **Liberate** to release it. Essential for stepping through flows during simulation. See [Galileo Simulation — §7](operations/galileo-simulation.md#7-extract-a-container-from-the-miniload).
Test-mode checkbox on a picking station in EasyS. When ticked, the container **does not leave automatically** after picking confirmation - the operator must click **Liberate** to release it. Essential for stepping through flows during simulation. See [Galileo Simulation - §7](operations/galileo-simulation.md#7-extract-a-container-from-the-miniload).
**MT / MTB (Transelevador de paletas)**
Monocolumn (MT) and Bicolumn (MTB) pallet stacker cranes. Heavy-duty variants of the miniload used for Euro-pallets. See [Mechanical Elements](concepts/mechanical-elements.md).
@@ -505,13 +505,13 @@ Spanish manufacturer and developer of EasyWMS and EasyS. Headquarters in Barcelo
Go-live event for a project. Pivot moment of [Git Branch Lifecycle](operations/git-branch-lifecycle.md): before MEP the CdP merges `develop`→`master` and deletes `develop`; Hypercare follows on a freshly-recreated `develop`.
**MSSCODE**
Internal Mecalux Gitea instance hosting all project repositories. Authentication via SSH key (ed25519) — see [SSH Keys Setup](operations/ssh-keys-setup.md). Cloning via SSH (not HTTPS) is mandatory once the SSH key is configured in Sourcetree.
Internal Mecalux Gitea instance hosting all project repositories. Authentication via SSH key (ed25519) - see [SSH Keys Setup](operations/ssh-keys-setup.md). Cloning via SSH (not HTTPS) is mandatory once the SSH key is configured in Sourcetree.
**MOR01 (Manufacturing Order)**
Inbound ERP message for manufacturing production orders. Triggers stock consumption of components and creation of finished goods. See [Manufacturing](modules/manufacturing.md).
**Montage sur demande**
Kit configuration flag (French: "on-demand assembly"). When `YES`, the WMS auto-creates an assembly work order at the integration of an outbound order containing a kit shortage. When `NO`, kit fabrication is only triggered by a manual or ERP-originated WOR — the WMS emits no automatic alert. See [Kits](concepts/kits.md#kit-shortage-handling).
Kit configuration flag (French: "on-demand assembly"). When `YES`, the WMS auto-creates an assembly work order at the integration of an outbound order containing a kit shortage. When `NO`, kit fabrication is only triggered by a manual or ERP-originated WOR - the WMS emits no automatic alert. See [Kits](concepts/kits.md#kit-shortage-handling).
**Movirack**
Mecalux mobile racking system where rack bays slide laterally to open aisles on demand. Five work modes: Manual, Auto, Timing, Autoparking, Autopicking. See [Movirack](modules/movirack.md).
@@ -533,7 +533,7 @@ EasyWMS add-on for carrier integration. Manages deliveries (carrier + consignee)
## N
**NEUT / ROUJE pattern (Split reception)**
Mecalux France reception split convention. Incoming stock is split between two complementary buffers at reception to enforce picking-vs-reserve separation : `NEUT` (neutral / picking-ready) and `ROUJE` (customs-held / reserve). Combines with four putaway strategies (direct-to-picking, picking + reserve, reserve only, customs-hold). See [Reception](concepts/reception.md#reception-split-strategy).
Mecalux France reception split convention. Incoming stock is split between two complementary buffers at reception to enforce picking-vs-reserve separation : `NEUT` (neutral / picking-ready) and `ROUJE` (customs-held / reserve). Combines with four putaway strategies (direct-to-picking, picking + reserve, reserve only, customs-hold). See [Reception](concepts/reception.md#reception-split-strategy-mecalux-france-pattern).
**Negative picking**
Automatic warehouse picking mode where an empty container is sent to a storage channel; the AS/RS picks the desired stock from the channel into the empty container. Used in LIFO channels. See [Picking](concepts/picking.md).
@@ -588,13 +588,13 @@ Picking mode where the operator picks directly into the final shipping box, elim
**Pick and Pass**
Picking mode where multiple operators each pick one zone; the client container passes from operator to operator along a conveyor or route until all lines are complete. See [Picking](concepts/picking.md).
**PIE station (Punto de Introducción de Entrada — Automatic Inbound Point)**
**PIE station (Punto de Introducción de Entrada - Automatic Inbound Point)**
The entry point of an automated warehouse. Validates dimensions, weight, and identity of incoming containers. Routes valid containers inward; rejects non-conforming containers to a rejection station. On the GALILEO side, the PIE is seen as a standalone station whose events trigger the `Galileo_PIEEventHandler_PR` workflow on EasyWMS. See [Stations](concepts/stations.md), [GALILEO Integration](architecture/galileo-integration.md) and [Reception](concepts/reception.md).
**PK conveyor / PK station (Picking conveyor)**
A picking workstation on the conveyor system. Operators work at a PC; containers arrive on the conveyor and are processed (picked, received, consolidated, counted) before continuing on the conveyor. PK station capacity is given per-route (unlike miniload TKs which give capacity per-station). See [Stations](concepts/stations.md) and [GALILEO Integration](architecture/galileo-integration.md).
**PKE station (Punto de Extracción de Salida — Picking Extraction Point)**
**PKE station (Punto de Extracción de Salida - Picking Extraction Point)**
Extraction point *from* a picking workstation, used on a "full" PK→PKE route for robotics simulation tests. Pairs with an ME (Manual Entry) target. See [Galileo Simulation](operations/galileo-simulation.md) and [Robotics Project Lifecycle](operations/robotics-project-lifecycle.md).
**PLC (Programmable Logic Controller)**
@@ -625,14 +625,14 @@ Illuminated display devices mounted at picking locations. Guide operators during
See **PTL**. Variant of PTL picking where devices are mounted on both shelves and equipment. See [Configuration Guide](operations/configuration-guide.md).
**ProductConversion (OutboundLine)**
Optional attribute of a shipping order line — can be `null` when the order specifies a container code but no item (e.g. a request for a specific support without product). Code review enforces a null-check. See [Code Review Process](operations/code-review-process.md).
Optional attribute of a shipping order line - can be `null` when the order specifies a container code but no item (e.g. a request for a specific support without product). Code review enforces a null-check. See [Code Review Process](operations/code-review-process.md).
---
## Q
**Poids balance / Poids calculé / Poids réel / Poids théorique (article) / Poids théorique (balance)**
The five container-level weight fields tracked by the WMS. *"Poids théorique"* is ambiguous in French — always disambiguate between **article** (from item master) and **balance** (from scale minus adjustments). See [Weights](concepts/weights.md).
The five container-level weight fields tracked by the WMS. *"Poids théorique"* is ambiguous in French - always disambiguate between **article** (from item master) and **balance** (from scale minus adjustments). See [Weights](concepts/weights.md).
**Quality lock**
A stock status applied to specific stock to block one or more operations (picking, replenishment, shipping, counting). Two subtypes: **receiving status** (applied at reception) and **user status** (applied manually or via ERP). See [Quality Control](concepts/quality-control.md).
@@ -648,7 +648,7 @@ One of three EasyWMS API families. Executes LINQ-based queries against Views or
Manufacturing module recipe types: `RCP01` = standard manufacturing recipe (components → finished good); `RCP02` = quartering recipe (split one item into portions). See [Manufacturing](modules/manufacturing.md).
**REAC station (Reactivation)**
Pallet Shuttle charging station variant — reactivates/charges a PS cart. See [Stations](concepts/stations.md).
Pallet Shuttle charging station variant - reactivates/charges a PS cart. See [Stations](concepts/stations.md).
**Receipt**
A WMS document that records the physical receipt of stock (containers and/or loose stock) within a reception session. Multiple receipts can be created against the same receipt order. Receipt is distinct from receipt order. See [Reception](concepts/reception.md).
@@ -684,13 +684,13 @@ Handheld or vehicle-mounted barcode scanning terminal used by warehouse operator
Outbound ERP message. Sent when a receipt order changes status (opened, partially received, closed). See [ERP Interface](concepts/erp-interface.md).
**Real Weight (Poids réel)**
Container weight field computed as `max(Calculated Weight, Theoretical Scale Weight)`. Acts as the "best known" weight — theoretical when no PIE pass has occurred, scale-derived once it has. Reported on shipping documents. See [Weights](concepts/weights.md).
Container weight field computed as `max(Calculated Weight, Theoretical Scale Weight)`. Acts as the "best known" weight - theoretical when no PIE pass has occurred, scale-derived once it has. Reported on shipping documents. See [Weights](concepts/weights.md).
**ROF (Receipt Order Fulfilled)**
Outbound ERP message. Sent when a receipt order is fully fulfilled (all lines received). Two variants: `ROF01` (standard) and `ROF02` (extended line-level detail — used when the inbound order was generated from a `Transfer` shipping order in the two-warehouse flow, and for returns). See [ERP Interface](concepts/erp-interface.md).
Outbound ERP message. Sent when a receipt order is fully fulfilled (all lines received). Two variants: `ROF01` (standard) and `ROF02` (extended line-level detail - used when the inbound order was generated from a `Transfer` shipping order in the two-warehouse flow, and for returns). See [ERP Interface](concepts/erp-interface.md).
**Routine (replenishment)**
French SmartUI label for the **Stockout / threshold-based** replenishment strategy — triggers when the picking location drops below its configured minimum. See [Replenishment](concepts/replenishment.md).
French SmartUI label for the **Stockout / threshold-based** replenishment strategy - triggers when the picking location drops below its configured minimum. See [Replenishment](concepts/replenishment.md).
**ROR (Receipt Order Request)**
Inbound ERP message. Creates a receipt order in EasyWMS. Multiple variants for supplier receipts, ASN pre-notifications, returns, and transfers. See [ERP Interface](concepts/erp-interface.md).
@@ -706,13 +706,13 @@ Inbound ERP message. Creates or updates a shipping route in EasyWMS. See [ERP In
## S
**SAC (Stock Analysis Classification)**
Outbound ERP message (`SAC01`) sent manually from SmartUI after running the ABC rotation analysis. Carries item code + suggested ABC class. The ERP uses it to update item classification. Not automatic — the WMS operator must explicitly trigger it. See [ERP Interface](concepts/erp-interface.md#module-specific-erp-messages).
Outbound ERP message (`SAC01`) sent manually from SmartUI after running the ABC rotation analysis. Carries item code + suggested ABC class. The ERP uses it to update item classification. Not automatic - the WMS operator must explicitly trigger it. See [ERP Interface](concepts/erp-interface.md#module-specific-erp-messages).
**SaaS (Software as a Service)**
Cloud-hosted deployment of EasyWMS on Amazon infrastructure. Includes VPN requirements, SaaS-specific API endpoints, and Amazon SaaS certification for mobile apps (Android 10 requirement for Marketplaces). See [System Architecture](architecture/overview.md).
**SCADA (Supervisory Control And Data Acquisition)**
Supervision UI layer of the automation installation. In Mecalux robotics, SCADA is distinct from both GALILEO (TMS logic) and EasyWMS (business logic) — it shows the physical machine state to operators and maintenance teams. See [GALILEO Integration](architecture/galileo-integration.md).
Supervision UI layer of the automation installation. In Mecalux robotics, SCADA is distinct from both GALILEO (TMS logic) and EasyWMS (business logic) - it shows the physical machine state to operators and maintenance teams. See [GALILEO Integration](architecture/galileo-integration.md).
**SCEM (Supply Chain Event Management)**
EasyWMS module for real-time event notification. Users subscribe to notification events and receive alerts via web, email, or SMS. See [Supply Chain Event Management](modules/supply-chain-event.md).
@@ -739,7 +739,7 @@ Spanish acronym for WMS. Used interchangeably with WMS in Mecalux Spain-originat
EasyWMS's web-based user interface (browser). Used by supervisors and managers for administration, monitoring, and configuration. Distinct from RFT (handheld terminal) screens. See [System Architecture](architecture/overview.md).
**Station update / Route update (GALILEO)**
Two status streams GALILEO pushes to EasyWMS roughly every 1–3 seconds. They carry real-time physical state (station busy/free, route status, movement progress) and are written in the Gateway log. Not `Event` messages — they do not trigger workflows, only update state. See [GALILEO Integration](architecture/galileo-integration.md) and [Galileo Troubleshooting](operations/galileo-troubleshooting.md).
Two status streams GALILEO pushes to EasyWMS roughly every 1–3 seconds. They carry real-time physical state (station busy/free, route status, movement progress) and are written in the Gateway log. Not `Event` messages - they do not trigger workflows, only update state. See [GALILEO Integration](architecture/galileo-integration.md) and [Galileo Troubleshooting](operations/galileo-troubleshooting.md).
**SOC (Shipping Order Confirmation)**
Outbound ERP message. Sent when a shipping order changes status (released, prepared, in progress, completed). See [ERP Interface](concepts/erp-interface.md).
@@ -763,7 +763,7 @@ GS1-standard 18-digit numeric identifier for a logistics unit (LPN). The default
Transaction prefix for stock-level events. Key types: `STK.RECEP` (received), `STK.MOVE` (moved), `STK.ADJ` (adjusted), `STK.PICK` (picked), `STK.SHIP` (shipped), `STK.REP` (replenished), `STK.MAN.PRODUCTION` (manufacturing). See [Transactions](concepts/transactions.md).
**SSCC prefix (change)**
Changing the SSCC prefix sequence is done in **EasyS** (the configurator). Open the warehouse, **double-click the warehouse name** to expose the SSCC/numbering panel, adjust the prefix and/or sequence number, save. Has no effect on already-created containers. See [Container](concepts/container.md#changing-the-sscc-sequence-prefix).
Changing the SSCC prefix sequence is done in **EasyS** (the configurator). Open the warehouse, **double-click the warehouse name** to expose the SSCC/numbering panel, adjust the prefix and/or sequence number, save. Has no effect on already-created containers. See [Container](concepts/container.md#changing-the-sscc-prefix).
**Stock assignment**
The allocation engine that decides which concrete stock lines fulfil each outbound order line detail, and which task type (picking, shipping, replenishment, virtual picking) will be created. Built around the `StockAssignProcess_*` workflows. See [Stock Assignment](concepts/stock-assignment.md).
@@ -794,13 +794,13 @@ A logical partition of a warehouse with independent stock management rules. Item
Container weight field computed as *Scale Weight − adjustments*. Initialised after the first PIE pass, then adjusted by subsequent stock moves. Input to Real Weight. See [Weights](concepts/weights.md).
**Theoretical Weight (Poids théorique article)**
Container weight field computed as *item-master unit weight × quantity + container tare*. Set at creation and on every adjustment. Note : the container tare is **frozen at creation** — changing the pallet-type weight in EasyS does not propagate. See [Weights](concepts/weights.md).
Container weight field computed as *item-master unit weight × quantity + container tare*. Set at creation and on every adjustment. Note : the container tare is **frozen at creation** - changing the pallet-type weight in EasyS does not propagate. See [Weights](concepts/weights.md).
**Transit buffer (intermediate buffer)**
EasyS element of type **Transport** whose sub-location is a **Buffer** (not Automatic) used to bridge two sub-warehouses served by different equipment groups. Pattern: reserve-equipment drops on the buffer, picking-equipment picks up. Critical detail: the sub-location is created as `Automatic` by default and must be manually changed to `Buffer`. See [Location](concepts/location.md#transit-buffer-between-sub-warehouses) and [Replenishment](concepts/replenishment.md#inter-sub-warehouse-replenishment-via-intermediate-buffer).
EasyS element of type **Transport** whose sub-location is a **Buffer** (not Automatic) used to bridge two sub-warehouses served by different equipment groups. Pattern: reserve-equipment drops on the buffer, picking-equipment picks up. Critical detail: the sub-location is created as `Automatic` by default and must be manually changed to `Buffer`. See [Location](concepts/location.md#transit-buffer-between-sub-warehouses) and [Replenishment](concepts/replenishment.md#inter-sub-warehouse-replenishment-via-an-intermediate-buffer).
**Transfer (SorType)**
Shipping order type for inter-warehouse transfers with a **reciprocal inbound order** at the destination. Unlike `DirectTransfer` (which only raises an ASN via ASO), `Transfer` creates a full ROR at destination carrying the source SOR reference ; the destination ROF02 (on close) reconciles the source. See [Order Outbound](concepts/order-outbound.md#transfer-two-warehouse-flow) and [ERP Interface](concepts/erp-interface.md).
Shipping order type for inter-warehouse transfers with a **reciprocal inbound order** at the destination. Unlike `DirectTransfer` (which only raises an ASN via ASO), `Transfer` creates a full ROR at destination carrying the source SOR reference ; the destination ROF02 (on close) reconciles the source. See [Order Outbound](concepts/order-outbound.md#transfer---two-warehouse-flow-inbound-order-created) and [ERP Interface](concepts/erp-interface.md).
**Task**
The atomic unit of work in EasyWMS. A task represents a single movement (container or stock from location A to location B). Tasks belong to a process (putaway, picking, replenishment, count, etc.) and follow a lifecycle: Pending → Generated → In Process → Finished/Canceled. See [Task](concepts/task.md).
@@ -814,8 +814,8 @@ French term for a carrier route. Integrated from a TMS via the `RUT` inbound ERP
**TK (Transstockeur / Stacker crane)**
Spanish/French term for a stacker crane serving a single miniload aisle. In GALILEO stations, a TK is seen as one station per miniload (capacity = number of container slots held on its forks). Opposite: a TKB is a bicolumn (double) miniload. See [Mechanical Elements](concepts/mechanical-elements.md) and [Stations](concepts/stations.md).
**TMS (Transport Management System — two meanings)**
Two distinct usages in EasyWMS docs: (1) **Robotics TMS**: GALILEO (production) or EasyS (simulator), which physically drives conveyors, stacker cranes and shuttles — see [GALILEO Integration](architecture/galileo-integration.md). (2) **Carrier TMS**: external carrier-booking software, integrates via Yard Management and Multi-Carrier.
**TMS (Transport Management System - two meanings)**
Two distinct usages in EasyWMS docs: (1) **Robotics TMS**: GALILEO (production) or EasyS (simulator), which physically drives conveyors, stacker cranes and shuttles - see [GALILEO Integration](architecture/galileo-integration.md). (2) **Carrier TMS**: external carrier-booking software, integrates via Yard Management and Multi-Carrier.
**Tracking (GALILEO)**
On the GALILEO side, a "tracking" is the live movement object (container + target station + progress). EasyWMS creates a tracking via the `GalileoMovTrackingCreateCommand` when it decides where a container should go; the tracking closes when GALILEO sends back an **End** message. Distinct from a WMS **task**, which may span multiple trackings. See [GALILEO Integration](architecture/galileo-integration.md).
@@ -847,7 +847,7 @@ Continuous maintenance team that delivers complementary "offers" via `release` b
The measurement unit for an item (piece, kilogram, liter, meter, etc.). EasyWMS supports multiple UoMs per item with conversion factors. The base UoM is used for all internal calculations; presentation UoMs are used at reception and picking. See [Product / Item](concepts/product-item.md).
**UserImagesURI**
Setting in the WMS `appsettings.json` that specifies the filesystem folder resolved for item pictures transmitted via `ITM01 <ItmPicture>filename.jpg</ItmPicture>`. Typical value: `C:/MLX/Data/Pictures/`. The WMS service account must have read access. See [ERP Interface](concepts/erp-interface.md#itm--image-fields).
Setting in the WMS `appsettings.json` that specifies the filesystem folder resolved for item pictures transmitted via `ITM01 <ItmPicture>filename.jpg</ItmPicture>`. Typical value: `C:/MLX/Data/Pictures/`. The WMS service account must have read access. See [ERP Interface](concepts/erp-interface.md#itm---image-fields).
**uGNA / uGNAConsole**
Mecalux command-line utility (`C:\Program Files (x86)\Mecalux\uGNA\uGNAConsole.exe`) used to export the WMS configuration / master data / parameters to XML files (option `-Z:<entities>`). Output is committed to the project Git in `..\test`. Distinct from the GNA service (interfacing layer). See [uGNA Data Export](operations/ugna-data-export.md) and [GNA, Services & License](operations/gna-services-license.md).