Sonnet - SAP Globe cloning and migration schedule

Começar. É Gratuito
ou inscrever-se com seu endereço de e-mail
Sonnet - SAP Globe cloning and migration schedule por Mind Map: Sonnet - SAP Globe cloning and migration  schedule

1. Prerequisite: MVM's hosting environment is ready to accomodate

1.1. Definition of sub-streams

1.2. Definition of minimum required services to make the MVM environment up and running and able to receive application

1.3. Build schedule for all sub-streams - considering the minimum required services to comply with Stage I. of SAP Globe cloning

1.3.1. Input: Technical planning procedure (HLD, LLD)

1.3.2. Input: Technical considerations, what lead time is necessary to implement the given service

1.3.3. Input: Procurement considerations, estimate what lead time is necessary to procure the given service

1.3.4. Input: Estimate the service management transition, including procurement procedures

1.4. Deliver accomodation-ready MVM IT environment

2. Prerequisite: IT Service management

2.1. Build up the SAP Globe application support services

2.1.1. Stage I. (The application is still hosted in EON/EDT environment) - specify and request the services from EDT services provider(s) on as-is basis

2.1.2. Stage II. (The application is migrated into MVM's IT environment) - specify, tender and contract for application support services from a local supplier

2.2. Build up the IT Infrastructure operation support services

2.2.1. Stage II. - Estimate OPEX cost and clarify procurement procedure to select new service provider

2.2.2. Stage II. - Execute the procurement procedure

2.2.3. Stage II. - Integrate new service provider into EER's ITIL processes and environment

3. Prerequisite: Understanding the cloning procedure

3.1. Stage I. - Cloning PG5 into PG8 and PG8 goes to/hosted in EON cloud

3.1.1. In-depth understanding the schedule and activities made by EDT central team

3.1.2. High level design of local actions and schedule for go-live

3.1.3. Define broad infra requirements

3.1.4. Concept of to-be application architecture

3.1.5. Prepare the list of integrated applications and services

3.2. Stage II. - SAP PG8 leaves EON cloud and goes to MVM cloud

3.2.1. In-Depth understanding of the tenant-to-tenant migration process

3.2.2. Investigate SAP Globe payment solution, what funtcional/product replacement is needed

4. Prerequisite: Buy-out contract

4.1. Concept alignment - Signing before closing, conditional contract, agree on contracting parties

4.2. Agreement on buy-out price

4.3. ExCo approval on contract at 05.06.2025.

5. Prerequisite: Depending services and applications

5.1. Stage I. - (SAP Globe remains hosted in EON/EDT einvironment) - Update the interfaces from other integrated apps towards SAP Globe clone (PG8) in order to maintain as-is integration

5.2. Stage II. - (Sap Globe clone is being migrated into MVM's environment) - Design migration of other integrated applications considering the interconnection b/w EON/MVM tenants

6. SAP Stream

7. Infra stream

8. Non-SAP Stream

9. PM/PMO

10. Prerequisite: Understand changes in business service management and corporate financials

10.1. Investigate the replacement of EBS Cluj

10.1.1. Assess whether MVM Services want / can take over the service portfolio

10.1.2. Deep-dive into service portfolio and assess what skills and capabilities are required to provide the services

10.1.3. Assess the replacement procedure, what lead time is required to procure the new service provider, and after procurement what time is needed to build a capable service team

10.1.3.1. Prepare the planning input to SAP Globe project - What time-gap is needed between Stage I. and II. in order to execute the transition of the service provider

10.2. Investigate the replacement of SAP Global Payment solution, its functionality and wheter it involvement in corporate finances

10.2.1. Clarify what expectation MVM HQ has regarding corporate finance management

10.2.2. Clarify what tools is required to replace the present solution, whether MVM has a viable toolset

10.2.3. Clarify the lifetime of the original SAP Payment solution in relation to Closing. Also, clarify whether the implementation of this tool is required before or after Stage I. goes live

10.3. Investigate whether new bank / bank account / credit account will be introduced after Closing

10.3.1. Build a broad concept what functions needs to be updated in SAP PG8

10.3.2. Clarify the timeframe / deadline of introducing the new banking services

10.3.3. Build a broad concept on implementation timeline