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:
2026-07-20 13:01:21 +02:00
parent 7496aafe64
commit 9ce6ae37be
88 changed files with 1769 additions and 1871 deletions
+12 -12
View File
@@ -16,12 +16,12 @@ last_compiled: "2026-04-17"
## Overview
Tense Flow (FR : *flux tendu*) enables picking directly from one or more source supports typically to prepare an outbound order **straight from reception** without first putting the stock away. The stock never hits a "normal" storage location : it is replenished to a dedicated buffer (FR : *poumon PREPARATION*) and consumed from there virtually.
Tense Flow (FR : *flux tendu*) enables picking directly from one or more source supports - typically to prepare an outbound order **straight from reception** without first putting the stock away. The stock never hits a "normal" storage location : it is replenished to a dedicated buffer (FR : *poumon PREPARATION*) and consumed from there virtually.
The flow combines:
1. A **tense-flow element** + an associated **buffer stage** (typically named `PREPARATION`).
2. A **replenishment task** from the source location(s) to the buffer, triggered at order release.
3. **Virtual picking** on the RF terminal the operator scans the source support + the newly created client container and declares the picked quantity.
3. **Virtual picking** on the RF terminal - the operator scans the source support + the newly created client container and declares the picked quantity.
4. A closing step that transfers the client containers to the shipping buffer.
## EasyS Configuration
@@ -31,7 +31,7 @@ The flow combines:
3. Associate the tense-flow element to the buffer as a `Delivery Stage`.
4. Configure the source locations (buffers and racks) with the option **"Allow origin of replenishement of tense flow"** set to true, otherwise the replenishment task generated at "Lancer en flux tendu" will find no candidate origins.
> ⚠️ Tense Flow always creates a replenishment task *towards the buffer first* the source locations must be eligible as tense-flow origins, not only as normal-flow origins.
> ⚠️ Tense Flow always creates a replenishment task *towards the buffer first* - the source locations must be eligible as tense-flow origins, not only as normal-flow origins.
## Functional Flow
@@ -48,7 +48,7 @@ RFT menu : **Tâches → Tâches à flux tendu**. Execute the task to move stock
RFT menu : **Ordres de sortie → Picking virtuel**.
1. Scan the **source support** (the pallet / container now at the buffer).
2. Create a **new client container** use the **"Générer SSCC"** button to assign a fresh SSCC.
2. Create a **new client container** - use the **"Générer SSCC"** button to assign a fresh SSCC.
3. Scan the new container or the destination location.
4. Enter the item + picked quantity (and any logistic attributes).
@@ -60,16 +60,16 @@ Once all the client containers are filled, transfer them to the `EXPEDITION` buf
## Common Errors
**"Lancer en flux tendu" creates no replenishment task** : either the outbound order is not released yet, or the source locations are not marked as `Allow origin of replenishement of tense flow`. Tense Flow replenishment uses a separate eligibility flag from the standard replenishment enable it on the candidate origins.
**"Lancer en flux tendu" creates no replenishment task** : either the outbound order is not released yet, or the source locations are not marked as `Allow origin of replenishement of tense flow`. Tense Flow replenishment uses a separate eligibility flag from the standard replenishment - enable it on the candidate origins.
**Virtual picking screen rejects the source scan** : the stock is not on the `PREPARATION` buffer yet the replenishment task must be executed first.
**Virtual picking screen rejects the source scan** : the stock is not on the `PREPARATION` buffer yet - the replenishment task must be executed first.
**Remaining stock is not proposed for putaway** : the tense-flow element is not associated to the buffer as a `Delivery Stage` re-check EasyS step 3.
**Remaining stock is not proposed for putaway** : the tense-flow element is not associated to the buffer as a `Delivery Stage` - re-check EasyS step 3.
## Related
- [Picking](picking.md) tense flow is a special picking mode that bypasses storage
- [Replenishment](replenishment.md) tense flow generates an upstream replenishment task with its own eligibility flag
- [Reception](reception.md) tense flow is commonly used to ship freshly received stock without storing it first
- [Outbound Order](order-outbound.md) tense flow is triggered on a released outbound order
- [Stations & Routes](stations.md) tense-flow buffer and element are configured alongside standard stations
- [Picking](picking.md) - tense flow is a special picking mode that bypasses storage
- [Replenishment](replenishment.md) - tense flow generates an upstream replenishment task with its own eligibility flag
- [Reception](reception.md) - tense flow is commonly used to ship freshly received stock without storing it first
- [Outbound Order](order-outbound.md) - tense flow is triggered on a released outbound order
- [Stations & Routes](stations.md) - tense-flow buffer and element are configured alongside standard stations