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)
2026-07-20 13:01:21 +02:00
parent 7496aafe64
commit 9ce6ae37be
88 changed files with 1769 additions and 1871 deletions
@@ -23,24 +23,24 @@ last_compiled: "2026-04-17"

 ## Overview

-Robotics projects — installations with mechanized hardware (miniload, TK, conveyors, APS, AGV…) — require tighter coordination than pure-software projects because physical installation, electrical work and IT integration run in parallel. This page covers the organizational roles, reference documents, planning artifacts, and the station-test milestone that validates the WMS ↔ GALILEO configuration before go-live.
+Robotics projects - installations with mechanized hardware (miniload, TK, conveyors, APS, AGV…) - require tighter coordination than pure-software projects because physical installation, electrical work and IT integration run in parallel. This page covers the organizational roles, reference documents, planning artifacts, and the station-test milestone that validates the WMS ↔ GALILEO configuration before go-live.

 ## 1. Project organization

 A robotics project pulls in multiple Mecalux stakeholders:

- **Chef de chantier** — site supervisor for the mechanical build
- **Chef de projet IT** — IT lead (WMS + automation integration)
- **Responsable électricité** — electrical lead
- **Responsable de projet** — master coordinator who aligns the above, owns the schedule, and guarantees everyone has the right information at the right time
+- **Chef de chantier** - site supervisor for the mechanical build
+- **Chef de projet IT** - IT lead (WMS + automation integration)
+- **Responsable électricité** - electrical lead
+- **Responsable de projet** - master coordinator who aligns the above, owns the schedule, and guarantees everyone has the right information at the right time

 The **Responsable de projet** is the single point of escalation; without them, gaps between disciplines (e.g. the rack is installed but the DTR has not been validated) lead to slippage.

-> The canonical organisational diagram for a robotics project is on [Confluence — Organisation d'un projet Robotique](https://easywmsfrance.atlassian.net/wiki/spaces/EF/pages/3000434425874).
+> The canonical organisational diagram for a robotics project is on [Confluence - Organisation d'un projet Robotique](https://easywmsfrance.atlassian.net/wiki/spaces/EF/pages/3000434425874).

-## 2. DTR — Document Technique de Référence
+## 2. DTR - Document Technique de Référence

-The **DTR (Document Technique de Référence)** lists every technical element required for an automated installation — hardware, IP addresses, services, accounts — along with the **responsibility split between Mecalux and the client**.
+The **DTR (Document Technique de Référence)** lists every technical element required for an automated installation - hardware, IP addresses, services, accounts - along with the **responsibility split between Mecalux and the client**.

 The DTR answers "who provides what and by when":
 - WMS server specs and OS
@@ -49,23 +49,23 @@ The DTR answers "who provides what and by when":
 - Services (Active Directory, DNS, NTP, SMTP)
 - Physical access and ports opened between segments

-The DTR template lives on [Confluence — DTR configuration réseau et matériel](https://easywmsfrance.atlassian.net/wiki/spaces/EF/pages/3000562515980) as a table format. Fill a copy per project; track outstanding client deliverables in Jira.
+The DTR template lives on [Confluence - DTR configuration réseau et matériel](https://easywmsfrance.atlassian.net/wiki/spaces/EF/pages/3000562515980) as a table format. Fill a copy per project; track outstanding client deliverables in Jira.

 ## 3. Planning (Miniload installation)

 Two reference plannings used on every miniload project:

-1. **Global installation planning** — overview of all phases (civil works → rack install → electrical → PLC commissioning → WMS integration → tests → go-live)
-2. **IT ROB planning** — the slice owned by the IT Robotics team (VM install, WMS deploy, EasyS configuration, Gateway, station tests, Hypercare)
+1. **Global installation planning** - overview of all phases (civil works → rack install → electrical → PLC commissioning → WMS integration → tests → go-live)
+2. **IT ROB planning** - the slice owned by the IT Robotics team (VM install, WMS deploy, EasyS configuration, Gateway, station tests, Hypercare)

-Both plannings live as Gantt images on [Confluence — Planning Installation Miniload](https://easywmsfrance.atlassian.net/wiki/spaces/EF/pages/3000567955477). Copy the Gantt at project kick-off and adjust dates to site reality.
+Both plannings live as Gantt images on [Confluence - Planning Installation Miniload](https://easywmsfrance.atlassian.net/wiki/spaces/EF/pages/3000567955477). Copy the Gantt at project kick-off and adjust dates to site reality.

 ## 4. Reference documentation

 | Document | Purpose | Location |
 |----------|---------|----------|
 | **Control_Communications_Interface_EN_GB.pdf** | All station types, event types, PIE flags | [MSSCC Automation docs](https://msscc.mecalux.com/documentation/Automation/master/ES/Documents/GalileoAWS/Control_Communications_Interface_EN_GB.pdf) |
-| **EasyWMSGateway_ControlInterface_EN.pdf** | Frame structure (low-level — used when a frame translation looks wrong) | [MSSCC services docs](https://msscc.mecalux.com/documentation/documentation/master/ES/docs_downloads/services/docs/EasyWMSGateway_ControlInterface_EN.pdf) |
+| **EasyWMSGateway_ControlInterface_EN.pdf** | Frame structure (low-level - used when a frame translation looks wrong) | [MSSCC services docs](https://msscc.mecalux.com/documentation/documentation/master/ES/docs_downloads/services/docs/EasyWMSGateway_ControlInterface_EN.pdf) |
 | **Stations index** | Station-specific behaviours and quirks | [MSSCC Stations index](https://msscc.mecalux.com/documentation/documentation/master/EN/areas/layout/stations/index.md) |

 Use them as the source of truth when writing the functional spec / interface document with GALILEO.
@@ -105,7 +105,7 @@ Context.StationRoutes.Where(sr => sr.Manager.ToString() == "Galileo")
        ? sr.StationTo.RealLocations.FirstOrDefault().LogicalCoordinate.Side : 0,
    AisleNumber = sr.StationTo.AisleNumber
 })
-// union with StationFrom — see full query on Confluence
+// union with StationFrom - see full query on Confluence
 .OrderBy(sr => sr.StationType)
 .ThenBy(sr => sr.StationNumber)
 ```
@@ -128,22 +128,22 @@ Verify during simulation by temporarily saturating each route and confirming the

 Consolidated checklist merging what each phase must deliver:

- [ ] DTR signed by client and Mecalux (hardware, IPs, services provisioned)
- [ ] VM installed, joined to the domain, reachable via VPN (see [VM Installation](vm-installation.md) / [VM Network Routing](vm-network-routing.md))
- [ ] EasyWMS deployed (see [First Deployment](first-deployment.md))
- [ ] EasyS layout matches the execution plan (racks, stations, routes, PLC Types)
- [ ] Gateway installed, `tenantCode` + `TokenUser` configured, port 3000 open
- [ ] Station test query matches GALILEO `.mgp` station list
- [ ] PLC Container Type / PLC Height Type coupling validated in simulation
- [ ] "Full" route checks passed (CME→TE, PKE→PK, ET→PS)
- [ ] End-to-end flows validated in EasyS (PIE → Miniload → PK → PS)
- [ ] Reject route + floor virtual route configured (no lost container)
- [ ] Automation Dashboard wired up with the client's monitoring (see [Automation Dashboard](../modules/automation-dashboard.md))
+- ☐ DTR signed by client and Mecalux (hardware, IPs, services provisioned)
+- ☐ VM installed, joined to the domain, reachable via VPN (see [VM Installation](vm-installation.md) / [VM Network Routing](vm-network-routing.md))
+- ☐ EasyWMS deployed (see [First Deployment](first-deployment.md))
+- ☐ EasyS layout matches the execution plan (racks, stations, routes, PLC Types)
+- ☐ Gateway installed, `tenantCode` + `TokenUser` configured, port 3000 open
+- ☐ Station test query matches GALILEO `.mgp` station list
+- ☐ PLC Container Type / PLC Height Type coupling validated in simulation
+- ☐ "Full" route checks passed (CME→TE, PKE→PK, ET→PS)
+- ☐ End-to-end flows validated in EasyS (PIE → Miniload → PK → PS)
+- ☐ Reject route + floor virtual route configured (no lost container)
+- ☐ Automation Dashboard wired up with the client's monitoring (see [Automation Dashboard](../modules/automation-dashboard.md))

 ## Related

- [GALILEO Integration](../architecture/galileo-integration.md) — protocol reference
- [Galileo Simulation](galileo-simulation.md) — EasyS bring-up, PIE injection, station sync
- [Galileo Troubleshooting](galileo-troubleshooting.md) — log analysis, faults
+- [GALILEO Integration](../architecture/galileo-integration.md) - protocol reference
+- [Galileo Simulation](galileo-simulation.md) - EasyS bring-up, PIE injection, station sync
+- [Galileo Troubleshooting](galileo-troubleshooting.md) - log analysis, faults
 - [VM Installation](vm-installation.md) · [VM Network Routing](vm-network-routing.md) · [First Deployment](first-deployment.md)
 - [Mechanical Elements](../concepts/mechanical-elements.md) · [Stations & Routes](../concepts/stations.md)