A very different road
The door you haven't opened with the biggest difference in steps from this one.
1. Get SAP's AI after moving to S/4HANA
Open door 1
Door 2Draft
Commit to RISE now, get Joule on ECC while moving
What this road promises
“Joule can work with ECC, for customers who started moving to RISE.”Source: The Register
Ask yourself:
1Start the RISE conversation with SAPAsk yourself:Is RISE right for us, or just the way to Joule?
Open the move to SAP's cloud ERP.
2Check the commercial conditionAsk yourself:Can we really move half the maintenance budget in the next cycle?
SAP asks for half your maintenance spend in cloud.
3Negotiate and signAsk yourself:What's in writing: which assistants, which dates?
Agree scope, dates and which AI.
4Set up the cloud connection to ECCAsk yourself:Do we have the skills for this, or is it another SI line item?
Connect ECC to SAP's cloud.
5Activate the first Joule assistants on ECCAsk yourself:Will these work on our customized ECC, or only on a clean demo system?
Turn them on, test on your processes.
6Run the migration in parallelAsk yourself:Same small team, now running a migration and an AI rollout together.
Migrate while the assistants run.
7Move AI to the new system after go-liveAsk yourself:Does what we set up now carry over, or do we redo it?
Switch AI use to the new system.
Where this road lands
- AI you get
- Some Joule assistants on ECC. List to verify.
- Time to production
- After RISE is signed. Date to verify.
- Cost
- RISE subscription, half your maintenance in cloud.
- Source: CIO.com (Independent press and analysts)
- Team load
- High. Migration and AI together.
- New systems
- RISE contract, BTP, cloud connection.
- Survives migration
- Built for the cloud ERP. To verify.
- Security and licensing
- Inside your SAP contract.
- Adoption risk
- Two changes at once.
Add this road to my plan
Open another door
Another road you haven't opened
One of the doors you haven't opened, picked at random.
3. Build AI on SAP BTP next to ECC
Open door 3