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

màj wiki avec retour MES lot-5 AD

Browse Source
This commit is contained in:
Arthur Ria
2026-05-20 09:41:27 +02:00
commit 23eb3f3c84
4106 changed files with 469381 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
wiki/operations/configuration-guide.md
+566
View File
@@ -0,0 +1,566 @@
---
title: "Configuration Guide"
type: operation
sources:
- configurations/reception_configuration01.md
- configurations/tense_flow_configuration01.md
- configurations/crossdocking/crossdocking_configuration01.md
- configurations/counts/count_configuration01.md
- configurations/picking/picking_PTL_configuration.md
- configurations/replenishments/picking_location.md
- configurations/replenishments/intermediate_stations.md
- configurations/replenishments/dynamic_replenishment_maxnumlots.md
- configurations/multi_carrier_shipping/multi_carrier_shipping_configuration01.md
- configurations/supply_chain_event_management/supply_chain_event_management_configuration01.md
- wiki/concepts/parameters.md
- wiki/concepts/putaway.md
- wiki/concepts/replenishment.md
- wiki/concepts/reception.md
- wiki/concepts/count.md
- wiki/concepts/crossdocking.md
- wiki/architecture/overview.md
related:
- concepts/parameters.md
- concepts/stations.md
- concepts/warehouse-designer.md
- concepts/putaway.md
- concepts/replenishment.md
- architecture/overview.md
- architecture/security.md
last_compiled: "2026-04-10"
---
# Configuration Guide
Deployment and setup guide for Easy WMS. Organized in dependency order: complete earlier sections before later ones. For parameter details, see [Parameters](../concepts/parameters.md). For troubleshooting, see [Troubleshooting](troubleshooting.md).
---
## 0. Pre-Deployment Checklist
Before configuring Easy WMS, verify the infrastructure:
| Item | Requirement |
|------|-------------|
| **IIS version** | IIS 10+ on Windows Server 2019 or later |
| **Application pools** | Main pool + Background Jobs pool + Integration pool — all configured as .NET CLR v4 |
| **Database** | Oracle 19c+ or PostgreSQL 13+ |
| **Environment variable** | `ASPNETCORE_ENVIRONMENT = Production` (not Development) |
| **WIFI** | 802.11n/ac coverage in all RF terminal work areas; separate VLAN for WMS traffic |
| **Label printers** | Zebra or equivalent configured per network port |
| **EasyS** | Layout configuration tool installed and validated before WMS go-live |
---
## 1. Warehouse Layout (EasyS)
All physical warehouse configuration is done in **EasyS** (the visual layout configurator), not in the WMS UI. Changes made in EasyS are deployed to the WMS as a "transfer" that must be validated.
### 1.1 Warehouse and Zone Setup
1. Create the **warehouse** entity with type (manual / automatic / mixed).
2. Define **sub-warehouses** if needed (physical separation or different logistics rules).
3. Create **storage zones** — group aisles by temperature, hazard class, or ABC zone.
4. Create **working zones** — assign equipment types with permission per process (reception, putaway, picking, replenishment, count).
### 1.2 Location Types
Configure location type properties:
- **Storage mode**: Container, loose stock, or both.
- **Storage logics** (12 flags): Allow picking, allow shipping, allow replenishment source/target, allow count, is crossdocking, etc.
- **Capacity**: Max weight, max containers, max height.
- **FIFO/LIFO**: Applied per location or location type.
Key location types to configure:
| Type | Use | Notes |
|------|-----|-------|
| Conventional (rack) | Standard pallet storage | Most common type |
| APS / APSFIFO | 3D automated shuttle | Requires APS3D module |
| Compact channel | Pallet Shuttle, mobile racking | Deep-lane storage |
| Dynamic | Flow rack | Separate FIFO entry/exit lanes |
| Buffer | Stage/transit locations | For ET stations |
| Dock | Inbound/outbound docking | Required for yard management |
| Picking dedicated (PDL) | First-level picking shelf | "Allow replenishment target" must be enabled |
### 1.3 Station Configuration
For each process, at least one station of the appropriate type is required:
| Station Type | Code | Required For |
|--------------|------|--------------|
| Dock | 34 | Inbound/outbound vehicle docking |
| Stage | 33 | Pre/post-dock staging |
| PIE | — | Automatic inbound sorter |
| PK conveyor | 2 | Picking/reception workstation |
| ALM | — | Storage station |
| ME/MU/MS | — | Multi-exit/multi-unit/multi-stock conveyors |
| ET (Transit) | — | Intermediate replenishment station |
| Consolidation | 17 | Order consolidation |
| Decision | 63 | Routing decision point |
| Workzone | 64 | Manual picking zone |
| PS charge | 66 (PSCharge) | Pallet Shuttle charging |
**Route configuration:** Every station pair that needs to exchange containers/stock requires an explicit route. Define: Origin → Destination → Transport type → Process → Task type.
### 1.4 Equipment Types and Instances
1. Create **equipment types** (forklift, hand truck, conveyor, AGV, etc.).
2. Assign process permissions per work zone.
3. Create **equipment instances** and assign to types.
4. Configure **container type compatibility** per equipment type.
5. For PTL: assign PTL controller to each PTL-equipped equipment.
---
## 2. Master Data Configuration
### 2.1 Container Types (LPN Types)
Defined in EasyS. Key attributes:
- Dimensions (L × W × H in mm), empty weight, max weight.
- Stackability, collapse distance (for width calculations).
- Division types (for automatic warehouse only).
### 2.2 Items
1. Create items in WMS UI or via **ITM ERP message**.
2. Assign mandatory profiles:
- **Reception profile** — required before any receipt can be created.
- **Shipping profile** — required before any shipping order line can be assigned.
- **Putaway profile** — optional; if absent, default warehouse strategy is used.
- **Count profile** — required for ABC-driven cycle counts.
3. Configure logistic attributes (lot, expiry, serial number, quality, etc.) per item or item type.
4. Set UoM and conversions; define base UoM clearly.
5. For cutting stock items: assign cutting profile with min/max quantities, cutting tolerance, and label configuration.
### 2.3 Suppliers, Carriers, Owners, Accounts
- Suppliers: required before receipt orders can be created.
- Carriers: required before shipping orders with carrier assignment are processed. Extended carrier attributes required for Multi-Carrier module.
- Owners / Accounts: required when Owner Extensions module is active (mandatory for 3PL billing and 3PL portal).
---
## 3. Reception Configuration
### 3.1 Core Parameters
| Parameter | Default | Effect |
|-----------|---------|--------|
| `ALLOW_CREATE_RECEPTION` | — | Allow WMS to create a receipt without a pre-existing order |
| `AutoCloseReception` | — | Auto-close receipt when all lines are fulfilled |
| `USE_EXCLUSIVE_RESERVE_STRICT_MODE` | — | Block ASN reception if referenced receipt order is missing |
| `RECEPTION_NUM_DAYS_PRODUCTION_DATE_MARGIN` | — | Minimum remaining shelf life required at reception |
| `LPN_CHECK_CODE_GS1LABEL` | — | Validate LPN code against GS1 SSCC format |
| `CONTAINER_CHECK_CODE_REPEATED_FOR_LABELS` | — | Prevent LPN code reuse (vs station codes, locations, aliases) |
### 3.2 PIE Station (Automatic Inbound)
Configure rejection handling — all PIE error types must have an explicit rejection route:
| Error Type | Destination |
|------------|-------------|
| Dimensional error | Rejection station |
| Weight error | Rejection station |
| Unknown container | Reconditioning station |
| ASN mismatch | Reconditioning station |
If receiving without RFT (containers enter PIE directly):
1. Configure a pre-PIE conveyor as a **Picking** station.
2. Assign a workstation (PC) to this conveyor.
3. Create route: PK → PIE → Inbound conveyor (or location table).
### 3.3 Dock Reception (Manual Warehouse)
- Each dock requires a stage for pre-docking buffers.
- Configure `Dock work mode`: Manual (operator decides putaway timing) or Automatic.
- Printer assigned to dock for LPN label printing.
### 3.4 Returns Reception
- Configure `RECEPTION_RETURN_ALLOW_AUTOSELECTION` to allow automatic item identification on returns.
- `RETURN_ALLOW_AUTOSELECTION` (eCommerce variant) governs eCommerce return flows.
---
## 4. Putaway Configuration
### 4.1 Strategy Sequence
Putaway strategies execute in order. The recommended sequence for most deployments:
1. **Assigned location** (PDL / item-assigned location) — highest priority.
2. **Channel filling** (compact, APS) — fill partially-occupied channels first.
3. **Storage zone by ABC** — A-class items near pick face; C-class items at depth.
4. **Crossdocking zone** (if applicable) — for items with `Enable crossdocking` active.
5. **Default zone** — catch-all for any remaining containers.
Key strategy attributes:
| Attribute | Description |
|-----------|-------------|
| Is crossdocking | Route eligible stock directly to XD locations |
| Loose stock | Place individual stock lines, not the container |
| Aisle balance | Distribute containers evenly across aisles |
| Relocation % | Maximum fill % before aisle stops accepting new containers |
### 4.2 Restrictions
Configure restrictions to prevent mixing incompatible items in the same location/aisle/zone:
- "Do not locate in same zone" — e.g., hazardous + non-hazardous.
- "Do not locate in same aisle" — e.g., temperature classes.
- "Do not fit on higher heights" — for fragile items.
- "Do not putaway adjacent" — for certain chemical incompatibilities.
### 4.3 PDL Creation (Picking Dedicated Locations)
PDLs are configured per item per location. Required settings:
- **Maximum stock level** — triggers top-off replenishment.
- **Minimum stock level** — triggers stockout replenishment.
- **Replenishment mode** — Container or Stock.
- **Enable automatic replenishment** — must be explicitly checked.
- **Delete when empty** — enable for seasonal items only.
For locations with drawers/boxes (small parts): use partition labels with pre-generated coordinates. Enable `RF_PICKING_CONFIRM_LOCATION` to require location scan at picking.
### 4.4 Intermediate Station Replenishment
When PDLs and stock source are in physically separate zones that cannot be directly routed:
1. Create ET (transit) stations between the zones with Buffer-type locations.
2. Enable "Container" storage mode at intermediate stations.
3. Configure equipment of type that allows replenishment tasks for each zone.
4. Create RF routes: source zone equipment → ET station; PDL zone equipment → ET station.
5. Even for loose stock replenishment: containers must be used when transiting through ET stations.
---
## 5. Picking Configuration
### 5.1 Core Picking Parameters
| Parameter | Default | Effect |
|-----------|---------|--------|
| `RF_PICKING_CONFIRM_LOCATION` | — | Require location scan before picking |
| `MAX_CONTAINER_WEIGHT` | — | Client container weight limit |
| `PICK_AND_PASS_ENABLED` | — | Enable Pick & Pass mode |
| `VOICE_ENABLED` | — | Enable voice-guided picking |
| `CUTTING_PRINTER` | — | Printer for cutting stock labels |
### 5.2 PTL Configuration (Pick To Light / Put To Light)
1. Install and configure the **PTL Service** (separate Windows service).
2. Create a warehouse station of type **Pick To Light** with a looped route (to itself).
3. For Put To Light: assign separate equipment group; create routes to both the main warehouse station and the PTL station (transport type: Pick To Light).
4. Assign PTL controller to each PTL-equipped equipment in EasyS.
5. For each extra location on the equipment: configure storage mode (stock or container, never both).
6. Container equipment extra locations: max containers = 1 per location; configure container type compatibility.
### 5.3 Workstation (PK) Configuration
- Assign a PC workstation to the PK conveyor station.
- Configure working mode: "All Modes", "Picking Only", or "Consolidation Only".
- For consolidation tasks: must be "All Modes" or "Consolidation Only".
- For PTL: ensure PTL service is running and controller assignments are correct.
### 5.4 Wave and Group Shipping Templates
- Create **shipping templates** in `Configuration > Shipping templates`.
- Templates define which orders are batched together (by carrier, priority, route, etc.).
- For grouped picking (wave): ensure all orders in the group share compatible container type requirements.
---
## 6. Replenishment Configuration
### 6.1 Strategy Types and Use Cases
| Strategy | Trigger | Best Used When |
|----------|---------|----------------|
| Top-off | PDL stock < maximum | Constant high-velocity picking |
| Stockout | PDL stock = 0 | Lower-frequency items |
| Shipping demand | Open outbound order has no PDL stock | On-demand preparation |
| Sub-warehouse | Sub-WH stock below min | Multi-zone warehouse separation |
### 6.2 Dynamic Replenishment
The `TryToReplenishProductLocations` background job runs automatically. Configure:
- Job schedule (recommended: every 5–15 minutes).
- `MAX_NUM_LOTS_REPLENISHMENT` — maximum lot lines per replenishment container (prevents mixing).
### 6.3 Replenishment from Picking Locations
Used for locations with boxes/drawers (small parts):
1. Assign minimum and maximum stock levels per PDL.
2. Enable `Stockout` strategy.
3. Place stock in a nearby storage location for FEFO/FIFO compliance.
4. If FIFO/FEFO required: configure the PDL's source location to "take from height" — the system maintains the FEFO sequence during replenishment.
---
## 7. Count Configuration
### 7.1 Location Prerequisites
For a location to be countable:
1. `Allow count` = True on the location in EasyS.
2. Count aisle defined for the location.
3. Equipment type must have count permission for the location's work zone.
4. Location not locked with a lock type that blocks counting.
5. Containers/stock not locked with types that block counting.
### 7.2 Lock Types for Count
Configure per lock type (in `Masters > Lock Types`):
- **Location lock types**: "Allow count" flag.
- **Container lock types**: "Allow count" flag.
- **Stock statuses**: "Allow count" flag.
### 7.3 Cycle Count Setup
1. Create a **count schedule**: item ABC class, warehouse zones, and frequency (how many items per iteration).
2. Create **count iterations** from the schedule: each iteration covers a subset of the total item population.
3. Generate **count order** from iteration: produces location or item count tasks.
4. Cycle count orders are **non-re-releasable** once canceled — create new orders if needed.
### 7.4 Double Validation
Enable per item (count profile) when count discrepancies require manager approval:
1. Activate `DOUBLE_VALIDATION_ACTIVE` or configure per item profile.
2. Count discrepancies enter "Pending Adjustment" state.
3. Manager validates or cancels from `Warehouse > Stock adjustments`.
4. COF ERP message sent only after all pending adjustments are resolved.
---
## 8. Crossdocking Configuration
Three mandatory configuration elements:
### Step 1 — Enable crossdocking on items
`Inventory > Items > item > "Enable crossdocking"` attribute = True.
### Step 2 — Configure crossdocking locations
In EasyS: activate **"Is crossdocking location"** on target locations.
### Step 3 — Create crossdocking putaway strategies
- Create strategies with **"Crossdocking"** attribute enabled.
- For placing loose stock (partial container): also enable **"Loose stock"** attribute.
- For placing whole containers: use a strategy with "Crossdocking" only (no "Loose stock").
- Strategies must be **enabled** (active) to be used.
**Reception requirement:** Crossdocking to warehouse requires receipt on an **equipment** (via RFT), not directly at a stage.
**Coverage check logic:** Before ordering crossdocking, WMS checks whether existing crossdocking locations already have sufficient stock to cover the open outbound line quantity. If yes, no crossdocking is ordered.
---
## 9. Quality Control Configuration
### 9.1 Stock Status Setup
1. Create stock statuses in `Masters > Lock Types > Stock Statuses`.
2. Per status, configure allowed/blocked operations (allow picking, allow shipping, allow replenishment, allow count, allow adjustment).
3. Set automatic unlock duration (days) for time-based unlocks.
### 9.2 Automatic Unlock Job
- Job: `Delete_StockStatusJob_PR`
- Recommended schedule: every 15 minutes.
- Ensure job is active in `Configuration > Jobs`.
### 9.3 Receiving Status at Reception
Configure per item reception profile:
- **Receiving status**: applied automatically at receipt (e.g., "Under inspection").
- **User status**: manually applied post-receipt (e.g., "Quarantine").
- STC message to ERP is sent at reception close (not at status application).
---
## 10. ERP Integration Configuration
### 10.1 Message Configuration
For each ERP message type to be processed, configure:
- **Message direction**: inbound (ERP→WMS) or outbound (WMS→ERP).
- **Processing mode**: synchronous or asynchronous.
- **Queue**: dedicated queue per message family is recommended.
Key message pairs to configure at go-live:
| ERP → WMS | WMS → ERP |
|-----------|-----------|
| ROR (receipt orders) | ROC (order status) |
| ASN (pre-notifications) | ROF (fulfilled) |
| SOR (shipping orders) | SOC (order status) |
| ITM (items) | SOF (fulfilled) |
| STR (stock lock) | STV (stock change) |
### 10.2 Integration Application Pool
- Separate IIS pool from main application.
- Monitor for stops — ERP messages queue if integration pool is down.
- Log location: check both IIS logs and WMS application logs.
### 10.3 API Keys
- Generate API keys per integration consumer (ERP, MCP server, external tools).
- Keys are regenerated in integration configuration.
- Use HTTPS for all API communication.
---
## 11. Module-Specific Configuration
### 11.1 Multi-Carrier Shipping
1. Create **extended carrier** records (carrier + Multi-Carrier specific fields: tracking files directory, manifest report, dock confirmation mode).
2. Configure **packaging stations** with source/destination routes.
3. Set up carrier tracking file archives directory on the server.
4. Configure **auto-selection rules** if automatic carrier assignment is needed.
5. For TNT: configure `Load manifest report` in extended carrier setup.
### 11.2 Supply Chain Event Management (SCEM)
Setup sequence:
1. Create **transports** (`Notifications > Configuration > Transports`): e-mail server, SMS gateway, or web endpoint.
2. Create **notification profiles** per user: transport + schedule (days/hours).
3. Create **filters** if needed (to limit alarms to specific conditions).
4. Subscribe users to relevant **notification events** (SCEM admin or user self-service).
Key events to subscribe for go-live monitoring:
| Event | Severity | When to Subscribe |
|-------|----------|--------------------|
| `Notification_GNAImportError` | Error | Always — ERP message parsing failures |
| AGV error codes (1001–2503) | Error | If AGV module active |
| PS fault/tilt | Error | If Pallet Shuttle module active |
| Stock failure on outbound order | Warning | Always — operational visibility |
### 11.3 Yard Management
Initial configuration sequence (10 steps):
1. Configure **commodities** (product categories for dock compatibility).
2. Configure **vehicle types**.
3. Create **carriers** with yard-specific fields.
4. Create **parking lots** (external waiting area zones).
5. Create **checkpoints** (physical security gates with attributes: weight control, advance/delay tolerance).
6. Create **docks** with compatibility rules (commodity × vehicle type).
7. Configure **work order types** (receipts and loads linkable to appointments).
8. Set up **ERP/TMS integration** (if external TMS sends appointments).
9. Configure **advance/delay windows** per yard or carrier.
10. Configure **auxiliary appointment types** for maintenance, cleaning, etc.
### 11.4 Labor Management (LMS)
1. Configure one **labor management profile per warehouse** (LMS is per-warehouse).
2. Define **processes** and their activities (maps to WMS task/process types).
3. Configure **equipment speeds** per equipment type (m/min for horizontal, m/min for vertical).
4. Set **warehouse layout dimensions** (aisle lengths, rack heights) used for target time calculations.
5. Choose **behavior mode** per process (no tolerance / allowed tolerance / fixed / flexible / ultra-flexible).
6. Enable RFT countdown display if desired.
### 11.5 3PL Billing
Prerequisites: **Owner Extensions** module must be configured first.
1. Assign owners to all receipt orders, shipping orders, and stock.
2. Create **billing contracts** per owner.
3. Within each contract, create **rules** (standard or custom).
4. Create **billing planners** (schedule: daily, weekly, monthly).
5. Configure **pre-validation workflow** if approval required before invoice generation.
### 11.6 AGV
1. Configure AGV equipment instances and types in EasyS.
2. Define AGV routes to all storage locations the AGVs will service.
3. Configure **load types**: 0 = Container, 1 = Pallet Shuttle.
4. Set up error notification subscriptions (AGV group) for operations staff.
5. Configure **RFT fallback mode** for manual operation during AGV downtime.
### 11.7 Slotting
1. Run initial **rotation analysis** (historical or current mode) to establish baseline ABC classification.
2. Review **golden zone** recommendations.
3. Configure **slotting profit formula** parameters (move cost, stay cost, daily rotation thresholds).
4. Enable **continuous slotting** background job for ongoing optimization.
5. Execute recommendations via **Slotting desk** (admin accepts/rejects suggested moves).
---
## 12. Security Configuration
### 12.1 Role Hierarchy Setup
Create roles from most to least permissive; assign permissions explicitly per role:
| Role | Primary Permissions |
|------|-------------------|
| SuperAdmin | Full system access; create roles |
| Administrator | Configure warehouse, masters, parameters |
| Manager | Approve adjustments, supervise operations |
| Operator | Execute WMS processes (reception, picking, shipping) |
| RF Operator | RFT-only access; assigned station roles |
| 3PL Client | Owner-filtered read access (requires Owner Extensions) |
| SCEM Admin | Notification subscription management |
### 12.2 Station Roles
Assign station roles to users/roles:
- Role determines which station types the user can log into from the RFT.
- Station role is checked at RFT login — rejected if not assigned.
### 12.3 Owner Isolation (3PL)
1. Enable **Owner Extensions** module.
2. Assign an owner to each user account intended for 3PL clients.
3. All master data created by the owner user is automatically prefixed with owner code.
4. Configure **3PL Portal** access per owner (read-only views: stock, orders, KPIs).
---
## 13. Parameter Reference Summary
Key parameters to review at each deployment. Full documentation in [Parameters](../concepts/parameters.md).
### Reception
- `ALLOW_CREATE_RECEPTION` — allow blind receipts
- `AutoCloseReception` — auto-close on completion
- `LPN_CHECK_CODE_GS1LABEL` — enforce GS1 SSCC format
- `RECEPTION_NUM_DAYS_PRODUCTION_DATE_MARGIN` — shelf life check at receipt
### Picking
- `RF_PICKING_CONFIRM_LOCATION` — enforce location scan
- `PICK_AND_PASS_ENABLED` — enable Pick & Pass mode
- `VOICE_ENABLED` — enable voice picking
### Replenishment
- `MAX_NUM_LOTS_REPLENISHMENT` — lot mixing limit per container
- TryToReplenishProductLocations job schedule
### Defragmentation
- `MAX_DEFRAG_TASKS` — max concurrent defragmentation tasks
- `MAX_OPTIMIZATION_DEFRAG_CHANNEL` — max channels optimized per run
- `MAX_DEFRAG_ATTEMPT` — retries before skipping a container
### AGV / Pallet Shuttle
- `PS_MAX_MINUTES_BATTERY_FULL_LOAD` = 300 (max battery life under load)
- `PS_MIN_MINUTES_BATTERY_LOAD` = 90 (minimum before return to charge)
### Multi-Carrier
- `MC_TRACKING_ARCHIVES_PATH` — carrier tracking files directory
- `MC_DEFAULT_CARRIER` — fallback carrier if auto-selection fails
---
## Related
- [Parameters](../concepts/parameters.md) — Complete parameter reference with all values
- [Troubleshooting](troubleshooting.md) — Error resolution guide
- [Stations & Routes](../concepts/stations.md) — Full station type reference
- [Warehouse Designer](../concepts/warehouse-designer.md) — EasyS-based layout configuration
- [Putaway](../concepts/putaway.md) — Strategy pipeline and configuration details
- [Replenishment](../concepts/replenishment.md) — PDL and strategy configuration details
- [System Architecture](../architecture/overview.md) — IIS, pools, and background jobs
- [Security](../architecture/security.md) — Roles, authentication, and permissions