# PRO1 - TMS



# PRO1 - TMS

##### Informations générales

**Code**: PRO1  
**Titre**: TMS  
**Type**: TPRO1 - Implementation  
**Statut**: En cours  
**Sponsor**: ENT1 - VT Supply Chain (Interne)  
**Réference du train**: Train 1  
**Méteo**: Moyenne  
**Taux avancement global estimé**: 5  
**Taux avancement délai**: 5  
**Date de début**: 2025-06-01 00:00:00  
**Date de fin estimée**: 2026-09-30 00:00:00  
**Date de fin réelle**: 2026-06-06 00:00:00  
**Budget OPEX estimé**: 200  
**Budget OPEX réel**: 250  
**Budget CAPEX estimé**: 300  
**Budget CAPEX réel**: 350  
##### Caractéristiques

<table id="bkmrk-caract%C3%A9ristiquenatur"><th style="background:#F5F5F5">**Caractéristique**</th><th style="background:#F5F5F5">**Nature**</th><th style="background:#F5F5F5">**Valeur**</th><tr><td>CARAC66 - Criticity (Texte)</td><td>Propriété</td><td>None</td></tr></table>

##### Contexte

OPmobility has decided to implement a central TMS (Transport Management System) solution that did not previously exist (either at the local or central level).

This solution requires process changes in the supply chain, the creation of ad-hoc department, and the implementation of an IT system supporting the entire process.

This solution will transform the transport operations’ company across Mexico, US/Canada, Europe, and the rest of the world (APAC and , South America regions).

##### Contributeurs

<table id="bkmrk-entit%C3%A9acteurr%C3%B4leent1"><th style="background:#F5F5F5">**Entité**</th><th style="background:#F5F5F5">**Acteur**</th><th style="background:#F5F5F5">**Rôle**</th><tr><td>ENT1 - VT Supply Chain (Interne)</td><td>Courseaux David</td><td>Architecte domain</td></tr></table>

##### ADR

<table id="bkmrk-adrdescription"><th style="background:#F5F5F5">**ADR**</th><th style="background:#F5F5F5">**Description**</th></table>

##### Key results

<table id="bkmrk-key-resultdescriptio"><th style="background:#F5F5F5">**Key result**</th><th style="background:#F5F5F5">**Description**</th><th style="background:#F5F5F5">**Type**</th><tr><td>ECART1 - Key result</td><td>This is a key result</td><td>Fonctionnel</td></tr></table>

##### Processus

<table id="bkmrk-processusprocess1---"><th style="background:#F5F5F5">**Processus**</th><tr><td>PROCESS1 - Processus</td></tr></table>

##### Processus: PROCESS1 - Processus

![](https://int.doc.archadia.io/uploads/images/gallery/2026-05/t2LGTQWc2SFd5nF5-embedded-image-is1gs8xx.png)##### Adhérences

<table id="bkmrk-projettypeimpactpro1"><th style="background:#F5F5F5">**Projet**</th><th style="background:#F5F5F5">**Type**</th><th style="background:#F5F5F5">**Impact**</th><tr><td>PRO1 - TMS</td><td>Projet interne</td><td>Impact on itself ;-)</td></tr><tr><td>External project - An external project</td><td>Projet externe</td><td>Has impact on TMS project</td></tr></table>

##### Démarche

Ceci est la démarche de mon projet

##### Contraintes

<table id="bkmrk-contraintedescriptio"><th style="background:#F5F5F5">**Contrainte**</th><th style="background:#F5F5F5">**Description**</th><tr><td>PROCONT1 - Constraint</td><td>A constraint</td></tr></table>

##### Exigences

<table id="bkmrk-exigencetypedescript"><th style="background:#F5F5F5">**Exigence**</th><th style="background:#F5F5F5">**Type**</th><th style="background:#F5F5F5">**Description**</th><tr><td>PROEX1</td><td>Non fonctionnelle</td><td>User characteristics: Users can access the solution via a web portal from a PC, laptop, or tablet. External partners use only the web portal, while admin users have direct access (e.g., SSH).</td></tr><tr><td>PROEX2</td><td>Non fonctionnelle</td><td>Location characteristics: The solution is intended for global deployment, with initial rollout in the following order: Mexico, US/Canada, EMEA, APAC, and SAO.</td></tr><tr><td>PROEX3</td><td>Non fonctionnelle</td><td>Load characteristics: Shipment volume will increase over time (approx.): 100,000 in 2026, 450,000 in 2027, and 470,000 in 2028. Final figures will be refined during workshops.</td></tr></table>

##### Sécurité

<table id="bkmrk-s%C3%A9curit%C3%A9descriptionp"><th style="background:#F5F5F5">**Sécurité**</th><th style="background:#F5F5F5">**Description**</th><tr><td>PROSECU2 - SEC2</td><td></td></tr><tr><td>PROSECU3 - SEC3</td><td></td></tr><tr><td>PROSECU4 - SEC4</td><td></td></tr><tr><td>PROSECU5 - SEC5</td><td></td></tr><tr><td>PROSECU6 - SEC5</td><td></td></tr><tr><td>PROSECU7 - SEC6</td><td></td></tr></table>

##### Plan d'occupation des sols impacté

![](https://int.doc.archadia.io/uploads/images/gallery/2026-05/uyJCy7svIEU9zgbo-embedded-image-vfkbqknw.png)##### Capacités

<table id="bkmrk-capacit%C3%A9typeimpactca"><th style="background:#F5F5F5">**Capacité**</th><th style="background:#F5F5F5">**Type**</th><th style="background:#F5F5F5">**Impact**</th><tr><td>CAP156 - Analyze performance</td><td>Modification</td><td>None</td></tr></table>

##### Cartographie des données impactée

![](https://int.doc.archadia.io/uploads/images/gallery/2026-05/PFWnVDGMyGbUIy75-embedded-image-5rwlhq1c.png)##### Objets métiers

<table id="bkmrk-objet-m%C3%A9tiertypeimpa"><th style="background:#F5F5F5">**Objet métier**</th><th style="background:#F5F5F5">**Type**</th><th style="background:#F5F5F5">**Impact**</th><tr><td>OM6 - Customers</td><td>Modification</td><td>None</td></tr></table>

##### Services

<table id="bkmrk-servicetypeimpactser"><th style="background:#F5F5F5">**Service**</th><th style="background:#F5F5F5">**Type**</th><th style="background:#F5F5F5">**Impact**</th><tr><td>SERV1 - Service</td><td>Modification</td><td>None</td></tr></table>

##### Solution applicative: PROSCEN1 - Applicative Solution

**Description**: This is the base scenario  
##### Paysage applicatif impacté

![](https://int.doc.archadia.io/uploads/images/gallery/2026-05/7yVUJGyPWragsPoL-embedded-image-8hucqfka.png)##### Applications

<table id="bkmrk-applicationtypeimpac"><th style="background:#F5F5F5">**Application**</th><th style="background:#F5F5F5">**Type**</th><th style="background:#F5F5F5">**Impact**</th><tr><td>APP954 - 4Flow</td><td>Modification</td><td>Introduction of a central TMS for transport planning, execution, optimization, and freight invoice control. Consumes master and demand data from SAP/EDI, performs transport and MRP related optimization, and sends outputs back to SAP. Carrier operational systems remain out of OPMobility responsibility.</td></tr><tr><td>APP955 - BOOMI</td><td>Modification</td><td>Extension of the integration layer to orchestrate SAP–TMS exchanges. Implements new SAP interfaces (master data, invoices) using the Boomi for SAP add on where available, or custom BAPIs for Lighting.</td></tr><tr><td>APP952 - SAP ECC6 Exterior</td><td>Modification</td><td>Activation and expansion of interfaces with the TMS ecosystem: master data exposure, exchange of MRP optimization results, integration of carrier invoices (posting and archiving), and generation of outbound logistics messages (plant-to-plant and returnable ASN).</td></tr></table>

##### Composants logiciels

<table id="bkmrk-composant-logicielty"><th style="background:#F5F5F5">**Composant logiciel**</th><th style="background:#F5F5F5">**Type**</th><th style="background:#F5F5F5">**Impact**</th><tr><td>CLOG321 - BOOMI (BOOMI)</td><td>Modification</td><td>impact composant logiciel</td></tr></table>

##### Flux logiques

<table id="bkmrk-flux-logiquetypeimpa"><th style="background:#F5F5F5">**Flux logique**</th><th style="background:#F5F5F5">**Type**</th><th style="background:#F5F5F5">**Impact**</th><tr><td>FLOG10 - Carrier invoice (BOOMI -&gt; SAP ECC6 Exterior)</td><td>Modification</td><td>impact flux logique</td></tr></table>