cloud era sap application development and 3 mode
TRANSCRIPT
Cloud Era SAP Application Development and 3ModeSAP FINUG Technology Seminar – 8.9.2016 – Tallinn, Estonia
Janne Vihervuori, Bilot
@JanneVihervuori
The near future is
overestimated. The far
future is underestimated.”Osmo Wiio, Laws of Future (1970-73)
Success is no longer about changing
strategies more often, but having
the agility to execute multiple
strategies concurrently.”Pierre Nanterme, CEO Accenture (2016)
Businesses have no idea what
the future will hold, whether
two days or ten years from
now.”Ron Tolido, SVP&CTO, Capgemini (2016)
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
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
SPEEDSlower thanRESPONSIVE, muchfaster than CORE. DevOps, Agile and similar ways of working.
COSTAverage cost, depends on the skillsrequirements.
RISKAverage business risk, low regression risk.
ENABLEMENT2
RESPONSIVE1
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
SPEEDSlow to very slow.
Highly dependant of the organizationalcapabilities, e.g. testing automation.
COSTChanges and development are of
high-cost. Proprietaryskills are required. Development is highlyIT-driven.
RISKTypically high-risk. Heavy regression effect.
ENABLEMENT2
CORE3
RESPONSIVE1
RESPONSIVE1
ENABLEMENT2
CORE3Undivided 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 specificskills. Changes in theRESPONSIVE layer are cheapbecause metaskills can beutilized.
SPEED
Speed and volume of changesincrease when moving towardsthe edge of the RESPONSIVE layer. There is no fast or slow, as all development should bedone as fast as possible.
RISK
Un-tested and unplannedchanges in the CORE can takedown a whole enterprise. And, vice-versa: changes gonewrong on the outer layershould affect a single business outcome at worst.
RESPONSIVE1
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
But wait! There’s more to 3Mode than3 Layers – contact us for more!
09/09/2016 www.bilot.fi 26
WHAT * END-POINTS1
HOW * PROCESSES2
WHY * STRATEGIES3