lint(standard): corrections completes mode standard
- Em dashes: 1712 remplaces par tirets simples (86 fichiers + _index.md, en-tete section Limagrain conserve) - Checklists: 24 '- [ ]' -> '- ☐' (3 pages operations, plus de todos Obsidian) - Ancres: 33 reparees (slugs GitHub + ancres HTML <a id> reconnues), 1 reciblee (manuel de reten) - related: tenseflow -> tense-flow, pie -> mechanical-elements, group.md retire (doublon shipping) - Registre: compteur global 122 -> 131 pages - Rapport racine _lint_report.md mis a jour (scan v2 + re-scan final: 0 anomalie) - Aucun fichier limagrain/ modifie (cloisonnement)
This commit is contained in:
+15
-15
@@ -30,7 +30,7 @@ last_compiled: "2026-04-17"
|
||||
|
||||
A location is any physical or virtual space capable of storing loose stock and/or containers within the warehouse. Locations are the fundamental spatial unit of Easy WMS: every piece of stock must have a location, every container must be placed in a location, and every movement task has a source and destination location.
|
||||
|
||||
Locations sit within a hierarchical spatial model: Organization → Warehouse (Site) → Zone → Aisle → Side → Column/Row. This hierarchy determines how putaway strategies are applied, how routes are calculated, and how work zones restrict equipment access. The configuration of each location — its type, storage mode, capacity, and logics — determines which processes can use it and how the system manages stock within it.
|
||||
Locations sit within a hierarchical spatial model: Organization → Warehouse (Site) → Zone → Aisle → Side → Column/Row. This hierarchy determines how putaway strategies are applied, how routes are calculated, and how work zones restrict equipment access. The configuration of each location - its type, storage mode, capacity, and logics - determines which processes can use it and how the system manages stock within it.
|
||||
|
||||
Locations are created and configured by implementers using the EasyS or Easy Assistant configuration tools. End users cannot create or delete physical locations; they can only manage stock within them and perform administrative operations such as locking, relabeling, or changing work zones.
|
||||
|
||||
@@ -80,10 +80,10 @@ In conventional rack and APS locations, if a container physically cannot be depo
|
||||
|
||||
When two sub-warehouses cannot share equipment (e.g., only high-reach forklift accesses a mezzanine, but it is barred from the ground-floor picking area), an **intermediate Buffer location** lets two different equipment types hand stock off to each other.
|
||||
|
||||
**Pattern** — `Sub-warehouse B reserve → Transit buffer → Sub-warehouse A picking`:
|
||||
**Pattern** - `Sub-warehouse B reserve → Transit buffer → Sub-warehouse A picking`:
|
||||
|
||||
- EasyS element of type **"Transport"** with aisles configured.
|
||||
- Its sub-location (double-click the transport element) is the actual buffer location. **EasyS creates it as type `Automatic` — it must be changed manually to type `Buffer`**, otherwise the RFT rejects the container scan with "le support n'existe pas".
|
||||
- Its sub-location (double-click the transport element) is the actual buffer location. **EasyS creates it as type `Automatic` - it must be changed manually to type `Buffer`**, otherwise the RFT rejects the container scan with "le support n'existe pas".
|
||||
- The transport sub-warehouse must be reachable by both equipment groups.
|
||||
|
||||
**Routing**:
|
||||
@@ -95,14 +95,14 @@ When two sub-warehouses cannot share equipment (e.g., only high-reach forklift a
|
||||
| Equipment group PICKING | Both sub-warehouses |
|
||||
| Equipment group RESERVE | Sub-warehouse B only |
|
||||
|
||||
Routes default to transport type `Galileo` — manually flip them to `RF` for a manual warehouse.
|
||||
Routes default to transport type `Galileo` - manually flip them to `RF` for a manual warehouse.
|
||||
|
||||
**Flow at runtime**:
|
||||
1. Replenishment task created from reserve (B) to picking location (A).
|
||||
2. RESERVE equipment (e.g., `CACES06`) takes the task → drops container on the transit Buffer.
|
||||
3. PICKING equipment (e.g., `PIK01`) picks the task in **Tâches → Tâches de réapprovisionnement** → drops stock at the picking destination.
|
||||
|
||||
See [concepts/replenishment.md](replenishment.md#inter-sub-warehouse-replenishment-via-intermediate-buffer) for the matching replenishment flow.
|
||||
See [concepts/replenishment.md](replenishment.md#inter-sub-warehouse-replenishment-via-an-intermediate-buffer) for the matching replenishment flow.
|
||||
|
||||
## Location coding
|
||||
|
||||
@@ -164,7 +164,7 @@ Key attributes visible in the "Locations" view:
|
||||
| Sub-warehouse | Sub-warehouse this location belongs to |
|
||||
| Coordinates | Aisle, side, X, Y, depth, stackability |
|
||||
| Maximum weight | kg capacity |
|
||||
| Height | m — used for container height compatibility checks |
|
||||
| Height | m - used for container height compatibility checks |
|
||||
| Last count date | When this location was last physically counted |
|
||||
| Full (manually marked) | Location excluded from putaway search; cleared when stock is added manually |
|
||||
| Crossdocking location | Flag for crossdocking eligibility |
|
||||
@@ -252,12 +252,12 @@ From the "Locations" view, users can modify (PC only):
|
||||
|
||||
## Related
|
||||
|
||||
- [[container]] — stored in locations; location type determines container compatibility and position tracking
|
||||
- [[stock]] — stock records are always linked to a location; location logics determine stock eligibility for picking/shipping/replenishment
|
||||
- [[putaway]] — putaway strategies target specific locations via zone/type/logic filters
|
||||
- [[replenishment]] — PDLs are locations with item assignment; replenishment source/target logics control eligibility
|
||||
- [[count]] — count processes filter on "Allow count" logic; count partition assignments link items to location positions
|
||||
- [[defragmentation]] — defragmentation moves stock between locations to consolidate and optimize space
|
||||
- [[task]] — all movement tasks have source/destination locations; location type determines coordinate reporting
|
||||
- [[crossdocking]] — crossdocking locations flagged with "Is crossdocking" are reserved for near-term outbound stock
|
||||
- [[stations]] — stations group locations into functional zones for routing and process assignment
|
||||
- [[container]] - stored in locations; location type determines container compatibility and position tracking
|
||||
- [[stock]] - stock records are always linked to a location; location logics determine stock eligibility for picking/shipping/replenishment
|
||||
- [[putaway]] - putaway strategies target specific locations via zone/type/logic filters
|
||||
- [[replenishment]] - PDLs are locations with item assignment; replenishment source/target logics control eligibility
|
||||
- [[count]] - count processes filter on "Allow count" logic; count partition assignments link items to location positions
|
||||
- [[defragmentation]] - defragmentation moves stock between locations to consolidate and optimize space
|
||||
- [[task]] - all movement tasks have source/destination locations; location type determines coordinate reporting
|
||||
- [[crossdocking]] - crossdocking locations flagged with "Is crossdocking" are reserved for near-term outbound stock
|
||||
- [[stations]] - stations group locations into functional zones for routing and process assignment
|
||||
|
||||
Reference in New Issue
Block a user