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

Caractéristique	Nature	Valeur
CARAC66 - Criticity (Texte)	Propriété	None

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

Entité	Acteur	Rôle
ENT1 - VT Supply Chain (Interne)	Courseaux David	Architecte domain

ADR

ADR	Description
ADR1 - ADR

Key results

Key result	Description	Type
ECART1 - Key result	This is a key result	Fonctionnel

Processus

Processus
PROCESS1 - Test processusProcessus

Processus: PROCESS1 - Test processusProcessus

Adhérences

Projet	Type	Impact
PRO1 - TMS	Projet interne	Impact on itself ;-)
External project - An external project	Projet externe	Has impact on TMS project

Démarche

 

Contraintes

Contrainte	Description
PROCONT1 - Constraint	A constraint

Exigences

Exigence	Type	Description
PROEX1	Non fonctionnelle	User characteristics: InUsers general,can the users will be able to useaccess the solution via a web portal from a PC, a laptoplaptop, or atablet. tabletExternal viapartners use only the web portalportal, of the solution. External partners will access the application only via the web portal; thewhile admin user willusers have direct access (such ase.g., SSH) to the solution..
PROEX2	Non fonctionnelle	Location characteristics: The solution willis beintended for global deployment, with initial rollout 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:order: Mexico, US/Canada, EMEA, APAC, SAOand SAO.
PROEX3	Non fonctionnelle	Load characteristics: The shipmentShipment volume will progressively increase yearly:over 2026:time 100(approx.): 100,000 shipments,2027:in 4502026, 450,000 shipments,2028:in 4702027, and 470,000 shipmentsin These2028. volumesFinal are approximative andfigures will be detailedrefined during the editor workshops.

Sécurité

Sécurité	Description
PROSECU1 - Security recommandation	A security recommandation

Plan d'occupation des sols impacté

Capacités

Capacité	Type	Impact
CAP156 - Analyze performance	Modification	None

Cartographie des données impactée

Objets métiers

Objet métier	Type	Impact
OM6 - Customers	Modification	None

Services

Service	Type	Impact
SERV1 - Service	Modification	None

Solution applicative: PROSCEN1 - Applicative Solution

Description: None

Paysage applicatif impacté

Applications

Application	Type	Impact
APP954 - 4Flow	Modification	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.
APP955 - BOOMI	Modification	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.
APP952 - SAP ECC6 Exterior	Modification	Activation and extensionexpansion of interfaces towardwith the TMS ecosystem: exposure of master data,data exposure, exchange of MRP optimization results, receptionintegration of carrier invoices for (posting and archiving,archiving), and generation of new outbound logistics messages (plant to plant-to-plant and returnable ASN).

Composants logiciels

Composant logiciel	Type	Impact
CLOG321 - BOOMI (BOOMI)	Modification	impact composant logiciel

Flux logiques

Flux logique	Type	Impact
FLOG10 - Carrier invoice (BOOMI -> SAP ECC6 Exterior)	Modification	impact flux logique