A successful enterprise Journey to Cloud requires more than technical execution, and we’ll help you learn what to consider, the pitfalls and how to succeed. We’ve helped many companies – in Australia and globally – execute their digital vision and accelerate change on their Journey to Cloud. We’ll share some of their experiences to help you discover how an optimised migration can transform your business.
Speakers:
Chris Fleishmann, Managing Director, Journey to Cloud Chief Architect
Attilio Di Lorenzo, Senior manager, Journey to Cloud Architect
2. CHRIS FLEISCHMANN
Managing director
Journey to cloud chief architect
ATTILIO DI LORENZO
Senior manager,
Journey to cloud architect
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
3. INTRODUCTION
APPLICATION LED MIGRATION CASE STUDY
TUMBLEWEED APPROACH
OUR CAPABILITY
RAPID DATACENTER EXIT CASE STUDY
MASS MIGRATION COMPONENTS
MULTIPLE APPROACHES
AGENDA
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
4. INFRASTRUCTURE ORCHESTRATION /
BROKERING
COST FOCUSSED.
NOT JUST COST
LINEAR PROJECTS
No longer constrained by the
infrastructure environment, can do SVT
while doing rev 2.0 of the same project
AGILITY AND
DEVOPS
SERVERLESS
1 1 0 1
0 0 1 0
1 0 1 0
APPLICATION LED
SaaS
PaaS
IaaS IaC
SAAS, PAAS,
IAAS, IAC
AUTOMATION
It’s now about:
No VM to VM
comparison.
If you get a chance to
rebuild, do it differently.
Infrastructure provided with
code (IaC).
Building environments
over and over with
minimal human footprint.
IT as a business enabler,
a self-service portal for
the business to consume.
ENABLEMENT
INTRODUCTION
CLOUD IS THE NEW NORMAL, WE’RE ALREADY
SEEING A PARADIGM SHIFT.
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
5. THE TIME IS NOW:
MIGRATE.
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
6. WHY MIGRATE?
1.Pay for what you need
2.Reduced CAPEX and reduced OPEX
3.Improved productivity
4.Improved security
5.Enter new markets / fail fast
6.Cost avoidance
7.Operational excellence
8.Business agility
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
9. MIGRATION AND DISPOSITION OPTIONS
Retain This is the “do nothing” option.
Re-host Typically on premises to encapsulated EC2 / VMs on a cloud provider.
Replace Replace one or more existing applications for new applications.
Refactor Application code or configuration changes are made to utilise cloud native services.
Rebuild Rebuild your solution on a providers application platform while discarding code from for an existing application platform.
Revise
Modify or extend the existing codebase to support legacy modernisation requirements, then use rehost or refactor options to
deploy to the cloud.
Retire Decommission and archive data as necessary.
MASS MIGRATION
JOURNEY OPTIONS:
Based off: http://www.gartner.com/newsroom/id/1684114
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
11. MULTIPLE MIGRATION APPROACHES
MANY PATHS
Each application can have a different path…
Decommission
Do not move
Define Business
Objectives / Strategy
Design, Build Cloud
Environment
Move the App
Infrastructure
Refactor
for Cloud
Provider
Rebuild Application
Architecture
VM Import
3rd Party Tools
Manually Move
App and Data
Determine
Migration
Process
Lift and Shift
(Minimal
Change)
Discover,
Assess (Enterprise
Architecture and
Applications)
Determine
Migration Path
Vendor
S/PaaS
(if available)
Move the
Application
Replatform
(typically legacy
Applications)
Rearchitect
Application
Recode
Application
Refactor
for AWS
Recode App
Components
Architect Cloud Environment
and Deploy App, Migrate Data
Application
Lift and Shift
Determine
Migration Process
3rd Party Migration Tool
Manually Move App and Data
Migration and
UAT Testing Signoff Operate
CutoverTuningPlan Migration
And Sequencing
Identify
Ops
Changes
Org/Ops
Impact
Analysis
Change
Management
Plan
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
13. PEXA’S APPROACH TO CLOUD MIGRATION
REPLATFORM AND REFACTORING TO AWS
PEXA’s approach was to use a lift-and-shift migration as an opportunity to start using
DevOps tools made available with AWS
Decommission
Do not move
Define Business
Objectives / Strategy
Design, Build Cloud
Environment
Move the App
Infrastructure
Refactor
for Cloud
Provider
Rebuild Application
Architecture
VM Import
3rd Party Tools
Manually Move
App and Data
Determine
Migration
Process
Lift and Shift
(Minimal
Change)
Discover,
Assess (Enterprise
Architecture and
Applications)
Determine
Migration Path
Vendor
S/PaaS
(if available)
Move the
Application
Replatform
(typically legacy
Applications)
Rearchitect
Application
Recode
Application
Refactor
for AWS
Recode App
Components
Architect Cloud Environment
and Deploy App, Migrate Data
Application
Lift and Shift
Determine
Migration Process
3rd Party Migration Tool
Manually Move App and Data
Migration and
UAT Testing Signoff Operate
CutoverTuningPlan Migration
And Sequencing
Identify
Ops
Changes
Org/Ops
Impact
Analysis
Change
Management
Plan
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
14. 2.01.0
PEXA EMBRACED DEVOPS
THE MOVE TO DEVOPS HAS EVOLVED WITH
MATURITY
PEXA moved from traditional waterfall approaches to a DevOps agile methodology.
Waterfall
Separate Dev, Test, Deploy Phases
DEV OPS DEV OPS DEV OPSDevOps
SEPARATE SILOS DEVOPS-AS-A-SERVICE EMBEDDED
Journey to Agile
• Projects run in 2 week sprints
• Each sprint containing
development and testing
• Specialised DevOps stream
required to perform deployment
activities
Fully Agile
• Development broken down into
squads
• Each squad has a different business
focus
• Each squad in a fully agile operate
model requiring no specialised
DevOps team to perform deployment.
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
15. PEXA TOOLING
CONTINUOUS DELIVERY PIPELINE
CI Server
Configuration
Management ServerBitBucket
SCM
• Product
• Infrastructure
• System
Configuration
• Security &
Compliance
Artifactory
(AMIs/Shared binaries)
Developers
Test Servers
Production
Servers
1. Initiate
2. Query product requirements
3. Apply infrastructure
4. Apply system configuration
6. Apply security & compliance mechanisms
5. Pull required
product change
set
7. Product
verification
testing
8. Query if old stack exists
9. Delete old stack (if exists)
10. Notify
Monitoring
and Alerting
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
18. ACCENTURE MASS MIGRATION SUCCESS STORY
PRESENTED AT RE:INVENT 2016 KEYNOTE
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
19. LARGE EUROPEAN UTILITY’S APPROACH
LIFT AND SHIFT FOR RAPID DATACENTER EXIT
This utility migrated more than 5,000 workloads at speed. More than 150 per week using a
core set of standardised AWS patterns.
Decommission
Do not move
Define Business
Objectives / Strategy
Design, Build Cloud
Environment
Move the App
Infrastructure
Refactor
for Cloud
Provider
Rebuild Application
Architecture
VM Import
3rd Party Tools
Manually Move
App and Data
Determine
Migration
Process
Lift and Shift
(Minimal
Change)
Discover,
Assess (Enterprise
Architecture and
Applications)
Determine
Migration Path
Vendor
S/PaaS
(if available)
Move the
Application
Replatform
(typically legacy
Applications)
Rearchitect
Application
Recode
Application
Refactor
for AWS
Recode App
Components
Architect Cloud Environment
and Deploy App, Migrate Data
Application
Lift and Shift
Determine
Migration Process
3rd Party Migration Tool
Manually Move App and Data
Migration and
UAT Testing Signoff Operate
CutoverTuningPlan Migration
And Sequencing
Identify
Ops
Changes
Org/Ops
Impact
Analysis
Change
Management
Plan
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
20. OPERATING
MODEL
DISCOVERY
& EXECUTION
BUSINESS
CASE
LARGE EUROPEAN UTILITY’S APPROACH
KEY ELEMENTS
Cloud transformation driving cost reduction and operating model simplification
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
…more economic benefits
than expected…
…strong planning and preparation…
...defined at project start and
refined iteratively...
• App deployment times down
from 6w to 12h
• Compute reduction of 35%
and more than 60% in
storage reduction.
• 30% reduction in tickets
• 20% of infrastructure
removed
• Business Unit and Country
driven discover and
execution to reduce risk and
minimise impact.
• Started simple to prove the
concept and earn trust with
the business, scaling with
size and complexity.
• Develop a new and efficient
operating model
consolidating legacy toolsets
and processes.
21. TWO COMMON METHODOLOGIES
WATERFALL APP BY APP
• Structured, consistent processes and results
• Highly measurable progress factors
• Planned scope and contractable costs
• Execution focussed, hard to enforce measurement and halt
activity, not aligned to ROI
• Medium adaptability
• High investment in pre-planning and team structure isn’t
always recoverable in highly dynamic migrations
• Low pre-planning investments are easy to recoup
• Highly flexible teams focused on the best migration for the
business
• Difficult to measure progress against long term goals
• Costs difficult to plan and manage across the life of the
migration
• Inconsistent process and results
+
-
+
-
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
22. Common pitfall Manifestation Functional result Manifestation
Extensive
migration, little
ROI
• Large migration executed
• TCO increased due to not
being able to shut down
legacy systems
• Increasing management
overhead of two platforms
No acceptance of the impossibility of knowing enough to
create a successful waterfall at start
Difficulty of accepting cost / time change into waterfall
• Operating model change
• Tools change
• Updating project plan
• Repetitive CR’s and req. Blow out
TCO developed without actually performing a migration, in
doing so the TCO will be incomplete
Analysis paralysis. An opposing problem to point 3.
• Spend too much time trying to make your TCO complete
with likely budget over-runs or prolonged project timelines.
Extensive
planning, stalled
migration
• Little or no migration and
no cloud value obtained.
• Significant investment in
planning is lost.
WATERFALL APPROACH
COMMON PITALLS AND FAILURES
Examining many migration projects that have followed the waterfall approach, there are
some common lessons.
Large remaining
datacenter
LARGE cloud
Large remaining
datacenter
No cloud
1
2
1
2
3
4
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
23. WATERFALL APPROACH
COMMON PITALLS AND FAILURES
Matthew Casperson*
LIFTING AND SHIFTING – IS IT SIMPLY A REBRANDING EXERCISE?
“…moving existing processes, infrastructure and mindsets from on premises and into the cloud prevents you
from harnessing the full potential that the cloud provides. I’ve seen this first hand. But I’ve also seen how
easy it is for even a simple lift and shift migration to fail, and nothing will kill your cloud strategy faster than the
time and money burned in a failed migration.”
* https://dzone.com/articles/to-quotlift-and-shiftquot-or-not-that-is-the-quest
„“
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
24. APP BY APP APPROACH
THE ‘ LIGHT ’ APPROACH
A second approach taken by clients focuses on moving applications, one application type
at a time.
Light weight teams with quick results
Focussed on quality for the
individual app
Low overhead
Flexibility / integrated decision ability
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
25. Common pitfall Manifestation Functional result Manifestation
Expensive,
disorganised, and
difficult to manage
cloud
Unique IMPLEMENTATIONS
COMPLICATING OPERATION,
MANAGEMENT, AND USE.
• Company security policies met
in varied and inconsistent
manner.
• Non standard naming
conventions.
• Tooling such as backup and
monitoring not consistent.
• Business units split between
legacy and cloud processes.
• Business processes remain the
same and are not modernised
for cloud.
Training isn’t created, executed or standardised. Results in
unexpected costs and confusion which are worse per app.
TCO
• Not created
• Not tracked
• Not standardised
Lack of coordinated program structure
• No programmatic feedback (solve same problems
repetitively)
• No coordinated reporting of results (what actually is
success?)
• Cloud application architecture differs for every application
• Technical implementations vastly diverse in terms of
languages, environments, APIs and connections
• No program level services (connectivity, issue resolution,
etc.)
• Highly siloed end results
Elongates the time to get to cloud vs DC closure.
APP BY APP APPROACH
COMMON PITALLS AND FAILURES
1 1
2
3
4
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
26. THE TUMBLEWEED APPROACH
(THE PREFERRED
APPROACH)
https://crazykittylove.files.wordpress.com/2013/06/tumbleweed.jpg
27. TUMBLEWEED APPROACH
CLOUD MIGRATION MATURITY MODEL
Consider the continuum of migration maturity models. You should target to be beyond stage 3.
STAGE 1:
AD-HOC
Few processes are defined
and are occasionally even
chaotic; success depends
on individual effort.
STAGE 2:
OPPORTUNISTIC
Basic project management
processes are established
to track cost, schedule, and
functionality. The necessary
process discipline is in place
to repeat earlier successes
on similar initiatives
STAGE 3:
REPEATABLE
The process for both
management and technical
activities is documented,
standardised, and integrated
into a standard software
process for the organisation.
STAGE 4:
MANAGED
Detailed measures of the
process/initiative are
collected. Process/initiative
is quantitatively understood
and controlled.
STAGE 5:
OPTIMISED
Continuous process
improvement is enabled by
quantitative feedback from
the process and from
piloting innovative ideas and
technologies.
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
28. Small scale diagram to follow as
we move through the model
Program sponsorship and governance
High level
business case
Strategic application
assessment
Select candidate
Applications
Agile team templates
Structure program
context
Establish feedback
loop
Feedback at start and end of every project
Training
Architecture
Connectivity
Licensing
Vendor support
I&AM
Operations
Application owner and business engagement
Migration
context
Project
sponsor
Business
sponsor
Sec, risk,
compliance
Technical
engineers
Ops
Application
engineers
App
owner
Feedback
TCOeval.
Agile team n…
Next
agile
team
Change
mgmt
Project
sponsor
Business
sponsor
Sec, risk,
compliance
Technical
engineers
Ops
Application
engineers
App
owner
Change
mgmt
TUMBLEWEED APPROACH
BEGIN WITH THE END IN MIND
A successful migration merges agile and waterfall approaches. Providing program level
components to agile teams.
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
29. You need data…
At this point you do not have enough data points to justify a full DC move, but hopefully you can focus on a
subset of applications that are good candidates.
Application TCO…
Each application will need its own business case. You cannot plan for these applications now nor know the details
of their needs to the right level.
Lower TCOInfrastructure
focussed
Higher flexibility
and agility
Faster time to
market
Scalability
and elasticity
Business case for migration;
TUMBLEWEED APPROACH
HIGH LEVEL BUSINESS CASE
Establish a High Level Business Case upon which the overall body of work can be evaluated.
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
30. Application
Package Custom
High SaaS maturity
and moderate
sensitivity
Low SaaS maturity /
high risk /
compliance
Low SaaS maturity /
market sensitivity
Old age legacy
High market
operational
sensitivity
Moderate market /
operational
sensitivity
Data compliance /
sensitive
Moderate data /
compliance
sensitivity
Data compliance /
sensitive
Moderate data /
compliance
sensitivity
IaaS
(on premises /
public)
Saas
IaaS
(public)
PaaS PaaS PaaS
TUMBLEWEED APPROACH
STRATEGIC APPLICATION EVALUATION
Evaluate your applications just enough such that you can group them by basic categories and make
some short term, high level decisions.
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
31. Simplifying it down to
three types:
Born in the cloud
archetype
Cloud ready
archetype
Cloud not ready
archetype
TUMBLEWEED APPROACH
START WITH A LIMITED SET
Choose 3-5 different types of applications that do not have data privacy issues, but are medium
complexity.
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
32. The main aim of this team is that they can sign off, can analyse build test and run their solution without needing to
engage other core areas of the business.
Create teams to execute your 3-5 applications, either in serial or parallel.
Serial executionParallel execution
Agile team n…
Project
sponsor
Business
sponsor
Sec, risk,
compliance
Technical
engineers
Ops
Application
engineers
App owner
Change
mgmt
TUMBLEWEED APPROACH
AGILE TEAM STRUCTURE
Create a team structure encompassing the resources necessary to execute the translation
of the target.
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
33. Program sponsorship and governance
Training
Architecture
Connectivity
Licensing
Vendor support
I&AM
Operations
Application owner and business enagement
Migrationcontext
Feedback
Tcoeval.
Provides exec oversight
Shared Program Level Services
Feedback and TCO after each
project completes
Agile team n…
Project
sponsor
Business
sponsor
Sec, risk,
compliance
Technical
engineers
Ops
Application
engineers
App owner
Change
mgmt
TUMBLEWEED APPROACH
STRUCTURE PROGRAM CONTEXT
Organise the context in which the agile teams will execute and a team to fund and oversee that context.
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
34. TUMBLEWEED APPROACH
ARCHITECTURE AND OPERATING MODEL
CONSIDERATIONS
Leverage the shared architecture and operating model patterns from the program. Make adjustments to
the architecture and operating model as you collect more evidence.
• Application level scope; An SAP environment is different to a web-based application, they should operate
differently.
• Re-use architecture and operating model procedures; vary only after sign off and consideration from
program level decisions
• Security roles; network vs admin vs application role should be consistent across multiple platforms, projects
and applications.
• Backup may be different; An SAP environment requires different back up procedures to an n-tier web
application where it may be stateless and self healing, but establish similar backup and restore procedures.
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
35. Architecture
Feedback
Tcoeval.
Operations
Architecture
Operations
Update the Operating Model and Reference Architectures as you collect
evidence
Re-Use Backup, Connectivity, Security, common patterns.
Re-Use the same Operating Model and Procedures where possible
Update/Adjust the Business Case
and TCO after each project
completes
The 3-5 projects you choose should form 3-5 reference
architectures that you start to harden and build out a
referenceable architecture for.
More than 25 architectures = a potential operating model
problem
Agile team n…
Project
sponsor
Business
sponsor
Sec, risk,
compliance
Technical
engineers
Ops
Application
engineers
App
owner
Change
mgmt
TUMBLEWEED APPROACH
ARCHITECTURE PATTERNS AND
FEEDBACK
Leverage the shared architecture and operating model patterns from the program. Make
adjustments to the architecture and operating model as you collect more evidence.
Program sponsorship and governance
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
36. TUMBLEWEED APPROACH
OVERALL BENEFITS
Realise the benefits:
• Update TCO assumptions, benefits, financial models (licensing other…)
• Update reference models; operating model and application and technical architecture patterns.
Result should be:
• Better understanding of timeline for launching an application or project on to cloud
• Better understand of architecture; back-up, connectivity (or issues with), security (what you can
and can’t protect), etc. etc.
• Better understanding of the financial model: TCO modelling more concrete.
• Traceability and accountability now enforced
• Now operating in at least two different environments.
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
37. Use the evidence captured and TCO savings to make the applications more cloud-aware
over time; in sprint 2, 3 4, … N. Continue to feedback your changes to the TCO and
business case. These are live documents.
Some but not all features:
Right sizing, use the clouds transparency to help address platform inefficiencies, stop
unwanted instances, use scaling, use different instance pricing models, choose applications
that are stateless and self healing, leverage storage classes, use managed services, offload
your architecture, consolidated billing, continuous price cuts and economies of scale
while evolving the others:
TUMBLEWEED APPROACH
ARCHITECTURE AND OPERATIONAL
BENEFITS
Business case and TCO detail captured…
Operating model and architecture patterns (up to 25) are now in place
But not forgetting other options in transitioning to cloud:
Retain
Rehost
Replace
Refactor Rebuild Revise
Retire
Selection
Traffic
Sellers Customer
experience
Lower
cost
structure
Lower
prices
Growth
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
39. Accenture
Research
Accenture
Ventures
Accenture
Studios
Accenture
Innovation centers
Accenture
Delivery centers
Accenture
Labs
Trends
Research &
Development
Investment &
open innovation
Solution
Innovation
Use cases
& assets
Industrialisation
Ideate through
thought leadership
Shape emerging
technologies
Prototype through applied
R&D projects
Build with speed and
agility
Scale re-use
With clients
Industrialise
Sales and delivery
ACCENTURE INNOVATION ARCHITECTURE
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
40. ACCENTURE AWS OFFERINGS SUPPORT SCALE
JOINTLY DEVELOPED AND DELIVERED SERVICES
AND SOLUTIONS
Run and operate via AWS managed services provider certified Accenture cloud platform
Analytics & big data
on AWS
Accelerated path to analytics
driven business relevant
outcomes.
The Accenture Insights Platform,
AWS Edition leverages AWS’ big
data and analytics services
An enabler for industries that
manage risk and compliance
challenges of regulated data in
the AWS cloud
Iot solutions and
services on AWS
Comprehensive industry
solutions and secure, scalable
IoT platform.
Industry-specific solutions include
Connected Home and Insurance
Telematics, with more to follow.
Solutions run on Accenture
Connected Products as a Service
(CPaaS) our broadly deployed and
open IoT platform architecture,
integrated with and optimised for
AWS IoT services.
Cloud transformation
services optimised for
AWS
Move existing applications to
and develop new applications
on AWS.
Services include:
• Cloud strategy
• Organisational and architecture
design
• Application migration and
refactoring
• Application development
services
• Migration ‘factory’ to automate
processes
SAP migration
to AWS
Simplify and accelerate the
journey of most customers
moving their SAP applications
to the cloud in the next 2-5
years.
Services include:
• SAP Implementation
• Cloud Infrastructure
Architecture and Setup
• SAP Run Support for Basis,
Functional, and Development
• Cloud Infrastructure Project &
Run Support
Cloud operating
model – security
solutions
Enhanced security solutions
focus on defence in depth
depth to secure client data and
applications emphasising
visibility and auditability.
Services include:
• Security assessment and
strategy for full migration or
hybrid AWS cloud scenarios
• Security architecture and
design
• Security expertise in cyber
defenses: intrusion and anomaly
detection, breach protection,
vulnerability assessment with
Accenture Cyber Defence
Platform
Strategic solutions
• Workplace-as-a-Service
• Accenture Digital Video
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION
41. ACCENTURE JOURNEY TO CLOUD
ACCENTURE'S MODULAR & SCALABLE AWS
OFFERINGS
Accenture AWS Offering Areas
Transformation Services
SAP on AWS
IoT
Big Data / Analytics
VDI / Workplaces
AWS Security
Accenture Cloud Platform
JOURNEY TO CLOUD
STRATEGY, ASSESSMENT AND ROADMAP CLOUD TRANSFORMATION AND MIGRATION
Cloud Journey Management
Cloud Migration Services
Cloud Application Modernisation
DevOps Services
Cloud Native Custom Development
PaaS Services
Cloud Operations
Security Operations
Cloud Optimization Services
Application Management
Business Process Operations
Application Migration Assessment & Planning
Infrastructure Assessment & Planning
Cloud Strategy
SAP on AWS
VDI /
Workplaces
CPaaS
on AWS
Cloud Discovery & Assessment Core Cloud Architecture
Application
Rehosting Application Optimisation
Application
Modernisation
AWS DevOps
Services
Cloud Native App
Dev
ADOP
on AWS
AIP
on AWS
AccentureCloud
Platform
AWS Security
AWS Security
CLOUD MANAGEMENT AND OPTIMISATION
MASS MIGRATION
COMPONENTS
MULTIPLE
APPROACHES
TUMBLEWEED
APPROACH
APPLICATION LED
MIGRATION CASE STUDY
RAPID DATACENTER
EXIT CASE STUDY
OUR
CAPABILITY
INTRODUCTION