OPM_Sandbox_1 - Transformation
Transformation
- PRO1 - TMS
- PRO1 - TMS
- PRO1 - TMS
- PRO1 - TMS
- PRO1 - TMS
- PRO1 - TMS
- ADR1 - adr1
- DETTE1 - ma dette
- PRO2 - TEST
- ADR2 - adr1
- DETTE2 - ma dette
- ADR3 - adr1
- PRO3 - un nouveau projet
- DETTE3 - test
PRO1 - TMS
PRO1 - TMS
Informations générales
Code: PRO1Titre: 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 |
|---|
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 |
|---|
ADR
| ADR | Description |
|---|
Key results
| Key result | Description | Type |
|---|
Processus
| Processus |
|---|
Adhérences
| Projet | Type | Impact |
|---|
Démarche
Contraintes
| Contrainte | Description |
|---|
Exigences
| Exigence | Type | Description |
|---|---|---|
| PROEX1 | Non fonctionnelle | 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. |
| PROEX2 | Non fonctionnelle | 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 |
| PROEX3 | Non fonctionnelle | 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. |
Sécurité
| Sécurité | Description |
|---|
Capacités
| Capacité | Type | Impact |
|---|
Objets métiers
| Objet métier | Type | Impact |
|---|
Services
| Service | Type | Impact |
|---|
Solution applicative: PROSCEN1 - Applicative Solution
Description: NonePaysage 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 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) |
Composants logiciels
| Composant logiciel | Type | Impact |
|---|---|---|
| CLOG328 - Boomi for SAP Add-on (SAP ECC6 Exterior) | Modification | To be installed in SAP for each BG except for Lighting |
Flux logiques
| Flux logique | Type | Impact |
|---|
PRO1 - TMS
PRO1 - TMS
Informations générales
Code: PRO1Titre: 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 |
|---|
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 |
|---|
ADR
| ADR | Description |
|---|
Key results
| Key result | Description | Type |
|---|
Processus
| Processus |
|---|
Adhérences
| Projet | Type | Impact |
|---|
Démarche
Contraintes
| Contrainte | Description |
|---|
Exigences
| Exigence | Type | Description |
|---|---|---|
| PROEX1 | Non fonctionnelle | 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. |
| PROEX2 | Non fonctionnelle | 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 |
| PROEX3 | Non fonctionnelle | 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. |
Sécurité
| Sécurité | Description |
|---|
Capacités
| Capacité | Type | Impact |
|---|
Objets métiers
| Objet métier | Type | Impact |
|---|
Services
| Service | Type | Impact |
|---|
Solution applicative: PROSCEN1 - Applicative Solution
Description: NonePaysage 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 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) |
Composants logiciels
| Composant logiciel | Type | Impact |
|---|---|---|
| CLOG328 - Boomi for SAP Add-on (SAP ECC6 Exterior) | Modification | To be installed in SAP for each BG except for Lighting |
Flux logiques
| Flux logique | Type | Impact |
|---|
PRO1 - TMS
PRO1 - TMS
Informations générales
Code: PRO1Titre: 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 |
|---|
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 |
|---|
ADR
| ADR | Description |
|---|
Key results
| Key result | Description | Type |
|---|
Processus
| Processus |
|---|
Adhérences
| Projet | Type | Impact |
|---|
Démarche
Contraintes
| Contrainte | Description |
|---|
Exigences
| Exigence | Type | Description |
|---|---|---|
| PROEX1 | Non fonctionnelle | 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. |
| PROEX2 | Non fonctionnelle | 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 |
| PROEX3 | Non fonctionnelle | 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. |
Sécurité
| Sécurité | Description |
|---|
Capacités
| Capacité | Type | Impact |
|---|
Objets métiers
| Objet métier | Type | Impact |
|---|
Services
| Service | Type | Impact |
|---|
Solution applicative: PROSCEN1 - Applicative Solution
Description: NonePaysage 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 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) |
Composants logiciels
| Composant logiciel | Type | Impact |
|---|---|---|
| CLOG328 - Boomi for SAP Add-on (SAP ECC6 Exterior) | Modification | To be installed in SAP for each BG except for Lighting |
Flux logiques
| Flux logique | Type | Impact |
|---|
PRO1 - TMS
PRO1 - TMS
Informations générales
Code: PRO1Titre: 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 |
|---|
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 |
|---|
ADR
| ADR | Description |
|---|
Key results
| Key result | Description | Type |
|---|
Processus
| Processus |
|---|
Adhérences
| Projet | Type | Impact |
|---|
Démarche
Contraintes
| Contrainte | Description |
|---|
Exigences
| Exigence | Type | Description |
|---|---|---|
| PROEX1 | Non fonctionnelle | 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. |
| PROEX2 | Non fonctionnelle | 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 |
| PROEX3 | Non fonctionnelle | 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. |
Sécurité
| Sécurité | Description |
|---|
Capacités
| Capacité | Type | Impact |
|---|
Objets métiers
| Objet métier | Type | Impact |
|---|
Services
| Service | Type | Impact |
|---|
Solution applicative: PROSCEN1 - Applicative Solution
Description: NonePaysage 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 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) |
Composants logiciels
| Composant logiciel | Type | Impact |
|---|---|---|
| CLOG328 - Boomi for SAP Add-on (SAP ECC6 Exterior) | Modification | To be installed in SAP for each BG except for Lighting |
Flux logiques
| Flux logique | Type | Impact |
|---|
PRO1 - TMS
PRO1 - TMS
Informations générales
Code: PRO1Titre: 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 |
|---|
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 |
|---|
ADR
| ADR | Description |
|---|
Key results
| Key result | Description | Type |
|---|
Processus
| Processus |
|---|
| PROCESS1 - Test processus |
Processus: PROCESS1 - Test processus
Adhérences
| Projet | Type | Impact |
|---|
Démarche
Contraintes
| Contrainte | Description |
|---|
Exigences
| Exigence | Type | Description |
|---|---|---|
| PROEX1 | Non fonctionnelle | 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. |
| PROEX2 | Non fonctionnelle | 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 |
| PROEX3 | Non fonctionnelle | 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. |
Sécurité
| Sécurité | Description |
|---|
Capacités
| Capacité | Type | Impact |
|---|
Objets métiers
| Objet métier | Type | Impact |
|---|
Services
| Service | Type | Impact |
|---|
Solution applicative: PROSCEN1 - Applicative Solution
Description: NonePaysage 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 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) |
Composants logiciels
| Composant logiciel | Type | Impact |
|---|
Flux logiques
| Flux logique | Type | Impact |
|---|
PRO1 - TMS
PRO1 - TMS
Informations générales
Code: PRO1Titre: 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
| 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 |
|---|
Key results
| Key result | Description | Type |
|---|---|---|
| ECART1 - Key result | This is a key result | Fonctionnel |
Processus
| Processus |
|---|
| PROCESS1 - Processus |
Processus: PROCESS1 - Processus
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
Ceci est la démarche de mon projet
Contraintes
| Contrainte | Description |
|---|---|
| PROCONT1 - Constraint | A constraint |
Exigences
| Exigence | Type | Description |
|---|---|---|
| PROEX1 | Non fonctionnelle | 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). |
| PROEX2 | Non fonctionnelle | Location characteristics: The solution is intended for global deployment, with initial rollout in the following order: Mexico, US/Canada, EMEA, APAC, and SAO. |
| PROEX3 | Non fonctionnelle | 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. |
Sécurité
| Sécurité | Description |
|---|---|
| PROSECU2 - SEC2 | |
| PROSECU3 - SEC3 | |
| PROSECU4 - SEC4 | |
| PROSECU5 - SEC5 | |
| PROSECU6 - SEC5 | |
| PROSECU7 - SEC6 |
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: This is the base scenarioPaysage 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 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). |
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 |
ADR1 - adr1
ADR1 - adr1
Informations générales
Code: ADR1Titre: adr1
Description:
Projet: None
Date maj statut: None
Date application: None
Date fin validité: None
Contexte: None
Dérogation: None
Statut cycle de vie: Proposé
Date cycle de vie: 2026-04-17 00:00:00
Cycles de vie
| Date | Statut |
|---|---|
| 2026-04-17 00:00:00 | Proposé |
Décideurs
| Nom | Prénom | Rôle |
|---|
Applications concernées
| Application | Commentaire |
|---|
DETTE1 - ma dette
DETTE1 - ma dette
Informations générales
Code: DETTE1Titre: ma dette
Description:
Etat: Assumée
Date déclaration: 2026-04-01 00:00:00
Date prévisionnelle remédiation: 2026-04-24 00:00:00
Date effective remédiation: None
Existant: None
Attendu: None
Justification/Risque
Justification écart: NoneResponsable: None
Nature: Aucun(e)
Risque associé: Aucun(e)
Niveau risque: Aucun(e)
Estimation coût
Coût estimé incident: NoneCoût estimé remédiation: None
Applications concernées
| Application |
|---|
PRO2 - TEST
PRO2 - TEST
Informations générales
Code: PRO2Titre: TEST
Type: TPRO1 - Implementation
Statut: A démarrer
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: 2026-04-30 00:00:00
Date de fin estimée: 2026-05-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
Contributeurs
| Entité | Acteur | Rôle |
|---|
ADR
| ADR | Description |
|---|
Key results
| Key result | Description | Type |
|---|
Processus
| Processus |
|---|
Adhérences
| Projet | Type | Impact |
|---|
Démarche
Contraintes
| Contrainte | Description |
|---|
Exigences
| Exigence | Type | Description |
|---|
Sécurité
| Sécurité | Description |
|---|
Capacités
| Capacité | Type | Impact |
|---|
Objets métiers
| Objet métier | Type | Impact |
|---|
Services
| Service | Type | Impact |
|---|
ADR2 - adr1
ADR2 - adr1
Informations générales
Code: ADR2Titre: adr1
Description:
Projet: None
Date maj statut: None
Date application: None
Date fin validité: None
Contexte: None
Dérogation: None
Statut cycle de vie: Proposé
Date cycle de vie: 2026-05-14 00:00:00
Cycles de vie
| Date | Statut |
|---|---|
| 2026-05-14 00:00:00 | Proposé |
Décideurs
| Nom | Prénom | Rôle |
|---|
Applications concernées
| Application | Commentaire |
|---|
DETTE2 - ma dette
DETTE2 - ma dette
Informations générales
Code: DETTE2Titre: ma dette
Description:
Etat: Assumée
Date déclaration: 2026-04-30 00:00:00
Date prévisionnelle remédiation: 2026-05-22 00:00:00
Date effective remédiation: None
Existant: None
Attendu: None
Justification/Risque
Justification écart: NoneResponsable: None
Nature: Aucun(e)
Risque associé: Aucun(e)
Niveau risque: Aucun(e)
Estimation coût
Coût estimé incident: NoneCoût estimé remédiation: None
Applications concernées
| Application |
|---|
ADR3 - adr1
ADR3 - adr1
Informations générales
Code: ADR3Titre: adr1
Description:
Projet: PRO1 - TMS
Date maj statut: None
Date application: None
Date fin validité: None
Contexte: None
Dérogation: None
Statut cycle de vie: Proposé
Date cycle de vie: 2026-05-15 00:00:00
Cycles de vie
| Date | Statut |
|---|---|
| 2026-05-15 00:00:00 | Proposé |
Décideurs
| Nom | Prénom | Rôle |
|---|
Applications concernées
| Application | Commentaire |
|---|
PRO3 - un nouveau projet
PRO3 - un nouveau projet
Informations générales
Code: PRO3Titre: un nouveau projet
Type: TPRO1 - Implementation
Statut: A démarrer
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: 2026-05-06 00:00:00
Date de fin estimée: 2026-05-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
Contributeurs
| Entité | Acteur | Rôle |
|---|
ADR
| ADR | Description |
|---|
Key results
| Key result | Description | Type |
|---|
Processus
| Processus |
|---|
Adhérences
| Projet | Type | Impact |
|---|
Démarche
Contraintes
| Contrainte | Description |
|---|
Exigences
| Exigence | Type | Description |
|---|
Sécurité
| Sécurité | Description |
|---|
Capacités
| Capacité | Type | Impact |
|---|
Objets métiers
| Objet métier | Type | Impact |
|---|
Services
| Service | Type | Impact |
|---|
DETTE3 - test
DETTE3 - test
Informations générales
Code: DETTE3Titre: test
Description:
Etat: En cours
Date déclaration: 2026-05-08 00:00:00
Date prévisionnelle remédiation: 2026-06-06 00:00:00
Date effective remédiation: None
Existant: None
Attendu: None
Justification/Risque
Justification écart: NoneResponsable: None
Nature: Aucun(e)
Risque associé: Aucun(e)
Niveau risque: Aucun(e)
Estimation coût
Coût estimé incident: NoneCoût estimé remédiation: None
Applications concernées
| Application |
|---|