Cloud era SAP Application Development and 3 mode
2 likes1,143 views
The document discusses the Cloud Era SAP Application Development and introduces the Bilot 3mode framework, which consists of three layers: responsive, enablement, and core. It outlines the complexity of enterprise IT, the need for agility in integrating new and old systems, and the benefits of rapid development through the responsive layer. Customer examples highlight how the framework is applied in real-world scenarios, emphasizing the importance of speed and risk management in changes to IT systems.
Cloud era SAP Application Development and 3 mode
- 1. Cloud Era SAP Application Development and 3Mode SAP FINUG Technology Seminar – 8.9.2016 – Tallinn, Estonia Janne Vihervuori, Bilot @JanneVihervuori
- 2. AGENDA 1. TUNE-IN 2. PROBLEM 3. THINK DIFFER3NT 4. SOLUTION 5. BENEFITS 6. CUSTOMER EXAMPLES
- 3. TUNE-IN New and old wise words. 09/09/2016 www.bilot.fi 3
- 4. The near future is overestimated. The far future is underestimated.” Osmo Wiio, Laws of Future (1970-73)
- 5. Every discussion we now have is about technology.” John Cryan, CEO Deutsche Bank (2016)
- 6. Success is no longer about changing strategies more often, but having the agility to execute multiple strategies concurrently.” Pierre Nanterme, CEO Accenture (2016)
- 7. Businesses have no idea what the future will hold, whether two days or ten years from now.” Ron Tolido, SVP&CTO, Capgemini (2016)
- 8. PROBLEM Enterprise IT. It is complex. 09/09/2016 www.bilot.fi 8
- 9. 9 OLD SYSTEMS, ON- PREMISE PLATFORMS. NEW SYSTEMS, CLOUD PLATFORMS.
- 10. 10 ITIL TOGAF DevOps Agile SOA…
- 12. THINK DIFFER3NT Three Simple Layers
- 13. ALL IMAGINABLE TOUCH-POINTS, DEVICES AND END-POINTS
- 15. CORE IS NOT ACCESSED FROM THE OUTER LAYER
- 17. All customer, user, IoT, etc. touch-points are found here. This is the layer where business should be able to develop and iterate as they like, at their own pace and speed – without restrictions. IT governance is zero to low, mainly security is to be considered. RESPONSIVE1 SPEED No speed-limits! Artifacts in the RESPONSIVE layer are treated individually. No methodoligal restrictions – anything can be applied! RISK Risk varies from low to nonexistent. All the risk should be within the individual artifacts. COST From the TCO point, cost of change is very low. Changes typically require cheap metaskills. RESPONSIVE1
- 18. This Digital Platform Ecosystem layer is the most important layer of 3Mode. It enables the various capabilities and services to be consumed and leveraged in the 1. RESPONSIVE layer. Development is done hand-in-hand with both business and IT. ENABLEMENT2 SPEED Slower than RESPONSIVE, much faster than CORE. DevOps, Agile and similar ways of working. COST Average cost, depends on the skills requirements. RISK Average business risk, low regression risk. ENABLEMENT2 RESPONSIVE1
- 19. Home of the essential data for your business models and strategies. It does not equal “ERP”, in which whole processes would reside; processes originate from CORE, but take their shape in the upper layers. You want to avoid development and forced changes at all cost in CORE! CORE3 SPEED Slow to very slow. Highly dependant of the organizational capabilities, e.g. testing automation. COST Changes and development are of high-cost. Proprietary skills are required. Development is highly IT-driven. RISK Typically high-risk. Heavy regression effect. ENABLEMENT2 CORE3 RESPONSIVE1
- 20. BENEFITS Put IT on the map. Develop productively. 09/09/2016 www.bilot.fi 20
- 21. RESPONSIVE1 ENABLEMENT2 CORE3 Undivided business logic and structured data. Best-of-breed systems. Cloud: IaaS. “Digital Core”. Core of ERP and applications. MDM. Structured Hadoop. Extending, enriching and providing CORE-layer logic or data. Cloud: PaaS. Application platforms. DW & Unstr. Hadoop, integration & API services. Consumption and exploration of ENABLEMENT- layer services. Cloud: SaaS/outer PaaS/None. Apps, websites, devices, end-points, sensors, touch-points, UI/UX of application platforms. ENABLEMENT2 CORE3 SPEED COST Changing the CORE is costly and requires domain specific skills. Changes in the RESPONSIVE layer are cheap because metaskills can be utilized. SPEED Speed and volume of changes increase when moving towards the edge of the RESPONSIVE layer. There is no fast or slow, as all development should be done as fast as possible. RISK Un-tested and unplanned changes in the CORE can take down a whole enterprise. And, vice-versa: changes gone wrong on the outer layer should affect a single business outcome at worst. RESPONSIVE1
- 22. RESPONSIVE1 ENABLEMENT2 CORE3 SAP S/4HANA SAP HCP SAP FIORI ENABLEMENT2 CORE3 SPEED RESPONSIVE1
- 24. Case City of Helsinki: Cloud-Era SAP- application development handbook
- 25. Customer case: 3Mode-based SAP E-commerce Release Management RESPONSIVE ENABLEMENT CORE ERP – System of record Hybris External UX Common Order-to-Cash configuration & development Commerce specific APIs and logic Commerce logic and integration Presentation and content Presentation & consumption Implications on release management Changes done purely in RESPONSIVE layer • Rapid release cycle possible due to low regression risk Changes involving the ENABLEMENT layer • Medium speed release cycle possible Changes involving the CORE layer • Option A: entire change done in a cycle dictated by CORE releases • Option B: CORE part done first, upper layer parts done later in shorter cycles
- 26. But wait! There’s more to 3Mode than 3 Layers – contact us for more! 09/09/2016 www.bilot.fi 26 WHAT * END-POINTS1 HOW * PROCESSES2 WHY * STRATEGIES3
- 27. Thank You! Janne Vihervuori Business Lead, Business Applications +358 40 5212 444 [email protected]