# 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**: None  
**Méteo**: Aucun(e)  
**Taux avancement global estimé**: 0  
**Taux avancement délai**: 0  
**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**: None  
**Budget OPEX estimé**: None  
**Budget OPEX réel**: None  
**Budget CAPEX estimé**: None  
**Budget CAPEX réel**: None  
##### 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></table>

##### Contexte

<span style="color:hsl(0, 0%, 0%);">OPmobility has decided to implement a central TMS (Transport Management System) solution that did not previously exist (either at the local or central level). </span>

<span style="color:hsl(0, 0%, 0%);">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. </span>

<span style="color:hsl(0, 0%, 0%);">This solution will transform the transport operations’ company across Mexico, US/Canada, Europe, and the rest of the world (APAC and <s>, </s>South America regions).</span>

##### Contributeurs

<table id="bkmrk-entit%C3%A9acteurr%C3%B4le"><th style="background:#F5F5F5">**Entité**</th><th style="background:#F5F5F5">**Acteur**</th><th style="background:#F5F5F5">**Rôle**</th></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></table>

##### Processus

<table id="bkmrk-processus-1"><th style="background:#F5F5F5">**Processus**</th></table>

##### Adhérences

<table id="bkmrk-projettypeimpact"><th style="background:#F5F5F5">**Projet**</th><th style="background:#F5F5F5">**Type**</th><th style="background:#F5F5F5">**Impact**</th></table>

##### Démarche

##### Contraintes

<table id="bkmrk-contraintedescriptio"><th style="background:#F5F5F5">**Contrainte**</th><th style="background:#F5F5F5">**Description**</th></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: In general, the users will be able to use the solution from a PC, a laptop or a tablet via the web portal of the solution. External partners will access the application only via the web portal; the admin user will have direct access (such as SSH) to the solution.</td></tr><tr><td>PROEX2</td><td>Non fonctionnelle</td><td>Location characteristics: The solution will be in long term to spread worldwide. In the context of the current document, the following country/region will be in the order withing the scope: Mexico, US/Canada, EMEA, APAC, SAO</td></tr><tr><td>PROEX3</td><td>Non fonctionnelle</td><td>Load characteristics: The shipment volume will progressively increase yearly: 2026: 100 000 shipments,2027: 450 000 shipments,2028: 470 000 shipments These volumes are approximative and will be detailed during the editor workshops.</td></tr></table>

##### Sécurité

<table id="bkmrk-s%C3%A9curit%C3%A9description"><th style="background:#F5F5F5">**Sécurité**</th><th style="background:#F5F5F5">**Description**</th></table>

##### Capacités

<table id="bkmrk-capacit%C3%A9typeimpact"><th style="background:#F5F5F5">**Capacité**</th><th style="background:#F5F5F5">**Type**</th><th style="background:#F5F5F5">**Impact**</th></table>

##### 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></table>

##### Services

<table id="bkmrk-servicetypeimpact"><th style="background:#F5F5F5">**Service**</th><th style="background:#F5F5F5">**Type**</th><th style="background:#F5F5F5">**Impact**</th></table>

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

**Description**: None  
##### Paysage applicatif impacté

![](https://int.doc.archadia.io/uploads/images/gallery/2026-04/rYcA1k6zxwmy92y0-embedded-image-vvxe6qan.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 extension of interfaces toward the TMS ecosystem: exposure of master data, exchange of MRP optimization results, reception of carrier invoices for posting and archiving, and generation of new 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>CLOG328 - Boomi for SAP Add-on (SAP ECC6 Exterior)</td><td>Modification</td><td>To be installed in SAP for each BG except for Lighting</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></table>