Cloud Migration Insights Forum is a 6 city roadshow, which aims to educate customers on the business benefits of migrating mission-critical workloads (Oracle, SAP, Windows workloads and VMware) on the AWS cloud, and the outcomes of which includes the ability to retire technical debt. In addition, New Zealand's energy supplier, Contact Energy, also shares their cloud migration journey and the efficiencies they were able to achieve following their migration of SAP onto AWS.
42. Disclaimer
43
This presentation may contain projections or forward-looking statements regarding a variety of items. Such forward-looking
statements are based upon current expectations and involve risks and uncertainties.
Actual results may differ materially from those stated in any forward-looking statement based on a number of important factors
and risks.
Although management may indicate and believe that the assumptions underlying the forward-looking statements are reasonable,
any of the assumptions could prove inaccurate or incorrect and, therefore, there can be no assurance that the results
contemplated in the forward-looking statements will be realised.
Furthermore, while all reasonable care has been taken in compiling this presentation, Contact accepts no responsibility for any
errors or omissions.
This presentation does not constitute investment advice.
44. 5
major generators producing ~96%
of New Zealand’s electricity
1
State-owned national transmission
grid operator
29
distribution businesses with some
150,000km of network lines
34
retail brands serving 1.7m
residential and 0.3m commercial
customers
1
½ hourly wholesale spot market
~86%
of electricity is produced from
renewable resources by 2016
70%
of electricity connections had smart
meters by end of 2015
385k
residential customers switched
their electricity provider in 2015
About New Zealand’s Electricity MarketThe New Zealand Electricity market
45. About Contact
46
21%
our share of the electricity
generation market in New Zealand
80%
the proportion of electricity
Contact generated from renewable
resources in FY17
$86/MWh
the electricity and gas netback we
received from retail sales in FY17
$27/MWh
the average cost to supply
electricity and gas to our
customers in FY17
20%
our share of the national electricity
and gas markets by ICP (41% of
LPG market)
562k
customer connections across
electricity, natural gas and LPG
+14
our net promoter score for the year
ending 30 June 2017
1st globally
out of over 5,000 companies
globally in Thomson Reuters
Diversity & Inclusion Index
$2.8bn
net assets
at 30 June 2017
BBB
S&P issuer rating
since 2002
70k
share and bond investors
at 30 June 2017
36%
gearing ratio as at
30 June 2017
47. Contact’s SAP landscape (Nov 2017)
48
SAP Gateway
MCFU
SAP CRM
CTI / IVR
Experian QAS
MCFU
SAP ECC
SAP IS-U
FICO, MM, PM
Excimp Emmax
VIM
Prometheus
DMS
MCFU
Experian QAS
Integr./Monit.
SAP Portal
(Internal)
SAP BO
SAP BW
OpenHub
Streamserve
OpenText
SAP SolMan
SAP PO
Control-M
48. Why did we move to the Cloud?
49
Where did we want to go?
• Lower cost infrastructure hosting with faster response times for end users
• High degree of agility that supports system and process innovation based on quick turn-around PoCs
• Customer friendly, mobile and responsive On-Line Self-Service (OLS) solution based on new SAP Multi Channel Foundation (MCFU)
• Faster SAP BW on HANA DB based reporting solution well integrated with data visualisation and analytics tools
Accelerating events
• In August 2015 Origin Energy, Australia, sold their majority shareholding in Contact Energy
• In October 2015 Contact’s most major ICT supplier contracts came to an end
An opportunity to make changes fast - Contact Energy’s ‘ICT Change and Transformation’ program (iCAT)
• Migration of all SAP systems from a dedicated AUS based data centre shared with Origin Energy to a Hybrid Cloud
• Migration of all non-SAP systems from a dedicated NZ based data centre to Private Cloud
• And many other things…
49. 50
iCAT – Contact’s SAP 2016 Migration Journey
Objectives
ü Separation of hosting resources
ü Move from dedicated Data Centre to Hybrid
Cloud
ü Move from HP-UX to Windows
ü Move from Oracle to SQL-Server
ü Move SAP BW to HANA DB
ü Move SAP UCES based online presence to MCFU
50. Nimbus - Moving SAP to Public Cloud in 2017
51
• Most of SAP hosted in Hybrid
Cloud with non-Prod in Public and
Pre-Prod/Prod in Private Cloud
• Currently only SAP BW is fully in
public Cloud with all tiers
• Moving all of SAP to Public Cloud
during on 2/3 Dec 2017
• Move to 3-tier SAP landscape with
DEV->TEST->PROD
• Using AWS native capability for DR
• No more single points of failure
• Drop F5 load balancers for ELB
• Implementing high degree of
automation
• AWS Cloud Formation
• SAP LAMA ‘light’ -> aka. ‘Alpaca’
51. Purpose
• Reduce our application hosting costs
• Improve our agility
Post iCAT
Optimisatio
n
Move
SAP and
MS Exchange
to Public
Cloud
Move
Oracle,
Tibco,
Websphere
to Public
Cloud
Move rest
of non-
SAP to
Public
Cloud
Establish
Cloud
Governance
Framework
Establish in
house
Cloud
DevOps
Capability
30 June 17 3 Dec 17 Aug 18 March 19Dec 17Dec 17
Current state
• Hybrid Cloud
• Hosting costs reduced by a third
• 2-3 weeks to stand up new system
(previously 12-15 weeks)
• No automation of standard service
requests
• 4 tier landscape for SAP
• < 48 hours for DR horizon for SAP
• Limited HA for some SAP
components
Future state (2019)
• Public Cloud for all business apps
• Hosting costs reduced to a third
• 2-3 days to stand up any new cloud
hosted system
• Automation of server management
related service requests
• Managed 3 tier landscapes
• < 6 hours DR horizon
December 2017
• Public Cloud for SAP
• Hosting costs halved
• 2-3 days to stand up a new SAP system
• Automation of SAP related server
builds, data refreshes & patching etc.
• 3 tier landscape for SAP
• < 6 hours for DR horizon for SAP
• Full HA for all SAP components
Contact’s Cloud Hosting Roadmap
52
15 Dec 16
Move
non-SAP to
Private
Cloud
22 Aug 16
Move
SAP to
Hybrid
Cloud
52. 53
* Infrastructure as code
Optimisation Innovation
Our focus to date
Our focus with Nimbus
Our focus 2018
Trial
Innovation
Cloud Services
Consume
Native Cloud
Services
Implement
Automation*
-> Agility
Implement
Automation*
-> Repeatability
Transfer Workload
(Compute &
Storage)
Create Digital
Innovation Space
Foundation Layer
(Network, Security Management, Connectivity, Data Management)
Establish internal Infrastructure DevOps team
(To date: furnished via external contractors
and some internal architecture resources)
Building Contact’s Cloud Capability
53. What lessons did we learn?
54
It works really well…
• AWS infrastructure not only ‘just works’ – Outperforms our NZ hosted private cloud
…with some limitations
• Some SAP features lack support on AWS – Research what is supported for your OS, DB and SAP release
• Some AWS features may not meet your expectations – Consider augmentation where required
You can save costs…
• Hosting costs to date have been halved – Will be down to a third by 2019
• For Contact SAP BW on HANA is significantly cheaper to run in AWS than relational DB BW on dedicated servers
• Beware that ‘T-shirt sizes’ play into design decisions – e.g. the curious case of SAP’s hostagent on Windows
• From 4 to 3 tier landscape and no more major change path into production – Stand up systems only when needed
…and this is just the beginning of a change journey
• Savings require hard work – Plan for an 3-6 months ‘optimisation phase’ and sustain your efforts
• Don’t think you can (or need to) optimise before go-live – Your thinking will be limited to your pre-cloud experience
• Invest in automation – Repeatability and speed in server build and management is an asset
• Make space for innovation – Agility gains only have real business value if readily available
54. 55
How to connect with me
E: hanno.schupp@contactenergy.co.nz
M: +64 21 916054
P: +64 4 462 1435
Li: https://nz.linkedin.com/in/hanno-schupp-aa5b19
E: hanno.schupp@contactenergy.co.nz
M: +64 21 916 054
P: +64 4 462 1435
L: https://nz.linkedin.com/in/hanno-schupp-aa5b19