Journey To The Cloud - Cloud Operating Models For more details see blog.contino.io/blog/designing-and-adopting-a-cloud-operating-model

1. www.contino.io
Journey To The Cloud In
Banking & Financial Services
Benjamin Wootton

2. ABOUT CONTINO
Continoare an enterprise DevOps & Continuous Delivery
consultancy with a presence in the UK and the USA.
We help large enterprise organisations and many of the worlds
biggest brands adopt DevOps and Continuous Delivery to add
speed, efficiency and quality to their software development
engines, and ultimately build a more vibrant software
development culture.
Based on our engagements with many global enterprise clients,
we have developed significant IP in how to transform to DevOps
and the cloud.

3. AIMS FOR WEBINAR
• Brief introduction to cloud
• The benefits for banks & financial services
• Cover the steps of the typical cloud journey
• Tips for success
• How Continosupport the cloud adoption journey

4. KEY CHARACTERISTICS OF THE CLOUD
• Infrastructure Is Provisioned On Demand Via a GUI Portal or APIs
• Instantly scale up with virtually no delay
• Instantly scale back down
• Flexible, consumption based billing model
• Infrastructure and platform as a service features
c.f. Typical Banking Process – Slow, Inefficient

5. PRIVATE VS PUBLIC
Public Cloud Providers
• Amazon Web Services
• Microsoft Azure
• Google Cloud
• Vendors e.g. IBM, Rackspace, Joyent, HP
Private Cloud
• VMWare
• OpenStack
• Vendors e.g. IBM, Rackspace, Joyent, HP
Hybrid
Software As A Service
• Salesforce
• Google Apps
• Dropbox / BOX.com
• Many more…
Platform As A Service

7. KEY TECHNOLOGY CHALLENGES IN
BANKING IN 2016
Constraints:
Cost Efficiency
Legacy
Regulatory Burden
Information Security
Technology Legacy
Demand:
Increased Technology Driven Business
Need For Speed, Agility & Innovation

8. HOW DOES CLOUD SOLVE THESE CHALLENGES
Infrastructure and applications on demand
The right capabilities scaled up and down and adjusted easily
More cost effective
Don’t need to purchase ahead of time
Reduced cost of ownership
Efficiency
Managed more efficiently using automation and APIs
Reduced cycle time for application delivery

9. A BANKS JOURNEY TO THE CLOUD
1. Strategic acceptance
2. Business case analysis
3. Risk analysis
4. Proof of concept
5. Contract negotiation
6. Rules of engagement
7. Early adopters
8. Industrialisation
9. Onboarding roadmap
10. Cloud first operating model
• Acceptance of value of the cloud as part of the technology strategy
• Senior level commitment to overcome the hurdles and begin the
journey
• Recognition that it’s different to on-premise infrastructure
• TIP: Remember to engage with the cloud vendors who will support
large enterprises (e.g. AWS & Microsoft Financial Services
Compliance Program)

10. Any migration is disruptive so we need to be aware of the challenges

11. A BANKS JOURNEY TO THE CLOUD
1. Strategic acceptance
2. Business case analysis
3. Risk analysis
4. Proof of concept
5. Contract negotiation
6. Rules of engagement
7. Early adopters
8. Industrialisation
9. Onboarding roadmap
10. Cloud first operating model
• Understand and model costs for transformation and
BAU run
• Work with finance to model move from CapEx to
OpEx
• Tie in with current data center strategy and
hardware refresh cycles

13. A BANKS JOURNEY TO THE CLOUD
1. Strategic acceptance
2. Business case analysis
3. Risk analysis
4. Proof of concept
5. Contract negotiation
6. Rules of engagement
7. Early adopters
8. Industrialisation
9. Onboarding roadmap
10. Cloud first operating model
• Data sovereignty
• Regulatory compliance
• Information security
• Business continuity

15. A BANKS JOURNEY TO THE CLOUD
1. Strategic acceptance
2. Business case analysis
3. Risk analysis
4. Proof of concept
5. Contract negotiation
6. Rules of engagement
7. Early adopters
8. Industrialisation
9. Onboarding roadmap
10. Cloud first operating model
• Vendor selection (Many vendors?)
• Focussed
• Gain initial network connection
• Stand up initial workloads
• Learn!

18. A BANKS JOURNEY TO THE CLOUD
1. Strategic acceptance
2. Business case analysis
3. Risk analysis
4. Proof of concept
5. Contract negotiation
6. Rules of engagement
7. Early adopters
8. Industrialisation
9. Onboarding roadmap
10. Cloud first operating model
• Pricing and commercials – tiered usage levels
• Service level agreements and quality of service
• Acceptable use policies
• Indemnification

19. A BANKS JOURNEY TO THE CLOUD
1. Strategic acceptance
2. Business case analysis
3. Risk analysis
4. Proof of concept
5. Contract negotiation
6. Rules of engagement
7. Early adopters
8. Industrialisation
9. Onboarding roadmap
10. Cloud first operating model
Data classification levels
• Public
• Internal
• Confidential
• Highly Confidential
• Regulatory
Data sovereignty
• Data is subject to the laws in the country in which it is hosted
• What if we are hosting our data outside of the country?
Which elements of the service will be made available and how they will
be used

20. A BANKS JOURNEY TO THE CLOUD
1. Strategic acceptance
2. Business case analysis
3. Risk analysis
4. Proof of concept
5. Contract negotiation
6. Rules of engagement
7. Early adopters
8. Industrialisation
9. Onboarding roadmap
10. Cloud first operating model
• Friction as they intersect with traditional processes
• Senior level support
• Requirement for upskilling, training and support
• Lighthouse project demonstrating success of cloud
to the rest of the organisation

21. A BANKS JOURNEY TO THE CLOUD
1. Strategic acceptance
2. Business case analysis
3. Risk analysis
4. Proof of concept
5. Contract negotiation
6. Rules of engagement
7. Early adopters
8. Industrialisation
9. Onboarding roadmap
10. Cloud first operating model
• Correct technical architecture and solution design (networks,
ID&A etc)
• Build a platform to be consumed at scale
• Federation with templates
• Cost control and cost optimisation
• TIP: Bring in expertise and work with your cloud providers
professional services partner to configure according to best
pratice

22. A BANKS JOURNEY TO THE CLOUD
1. Strategic acceptance
2. Business case analysis
3. Risk analysis
4. Proof of concept
5. Contract negotiation
6. Rules of engagement
7. Early adopters
8. Industrialisation
9. Onboarding roadmap
10. Cloud first operating model
• Evaluating the application portfolio
• Deciding what do we need to remediate, lift & shift
and re-architect

23. A BANKS JOURNEY TO THE CLOUD
1. Strategic acceptance
2. Business case analysis
3. Risk analysis
4. Proof of concept
5. Contract negotiation
6. Rules of engagement
7. Early adopters
8. Industrialisation
9. Onboarding roadmap
10. Cloud first operating model
• Understanding how the cloud will be deployed, managed and
used within the organisation
• Defines key processes for managing infrastructure and
applications
• Defining the changes to people & process structures
• TIP: Iterate and learn rather than get stuck in
analysis/paralysis

24. ADOPTING A CLOUD OPERATING MODEL
DevOps processes and approaches are the optimal approach to use and manage the cloud.
DevOps involves using small cross functional teams which get developers and operations working together to
manage the cloud through a software defined, repeatable, automated continuous delivery pipeline.
The aim is to remove central IT as a bottleneck, whilst ensuring that quality, governance and security are enhanced.
When this happens, it should be simpler to continuously deliver applications, increasing the organisations ability to
innovate in the market.
Developer Developer Developer IT Operations Fully Automated
Continuous Delivery Pipeline

25. Cloud Infrastructure Management: Key processes for provisioning, asset tracking and managing compute,
storage, networking and other platform assets
Cloud Operations: Key BAU technical processes which will be carried out on top of the cloud
Infrastructure platforms
Cloud Application Portfolio (Run) - Key processes describing how we will manage and proactively
support cloud based applications
Cloud Application Portfolio (Change) - Key processes for onboardingbrownfield and greenfield cloud
based applications and evolving them over time
FinancialModel-Howwewillaccountfor,allocateandmanagecostofcloud
infrastructureandmanagement
SecurityandControlsModel–Howwewillcontrol,govern,auditandsecureour
cloudbasedenvironmentsandapplications
PeopleModel-Howourpeopleandpartnersworktogethertodeliverand
supportourcloudbasedinfrastructure&applications
Compute Storage Network Data
IAAS/PAAS
Model
Environment
Management
Patch
Management
Network
Management
Backups And DR
Configuration
Management
Cloud Readiness
Cloud
Remediation
Cloud
Optimisation
Architecture
Governance
Change Control
Support Model
Proactive
Monitoring
Automation
TeamStructure&
Organisational
Design
Roles,Skills,
Learning&
Development
Responsibilities&
Accountabilities
Approvalsand
CostControl
Chargeback
Cost
Optimisation
Identity&Access
Management
ChangeControl
Process
Encryption&
Compliance
Data
Management
Cloud ApplicationManagementCloud InfrastructureManagement
’Cross Cutting’ Concerns
www.contino.io
Scope Of A Cloud First Operating Model
Automation

26. Case Studies - Tesco Bank
“In order to differentiate ourselves and offer greater services to our customers, we
need the ability to innovate, we need to be able to fail fast and fail cheap and simply be
more creative”
"And this means we need more speed and an infrastructure delivery cycle measured in
months is not going to support our ambitions.”
http://www.computerworlduk.com/cloud-computing/how-tesco-bank-has-adopted-
aws-cloud-as-business-as-usual-in-eight-months-3629767/

27. Case Studies – Capital One
”AWS enables us to operate even more securely in the public cloud than our own data
centers” – Rob Alexander, CIO
“Leveraging AWS, Capital One is shrinking its data center footprint. It will be down to
three by the end of 2018, compared to eight in 2014.”
http://www.zdnet.com/article/ge-capital-one-give-aws-the-rub-at-reinvent/

28. How Contino Support The
Cloud Journey

29. OUR APPROACH TO THE CLOUD
Contino have a unique approach to helping companies succesfully consume cloud technologies.
• Enterprise Focus: We focus on large scale enterprise clients, and have the skills and experience in helping them
with the security, governance and enterprise architecture issues associated with cloud.
• Consuming cloud with DevOps: We help our clients adopt DevOps so they consume cloud through a DevOps
model which brings in high degrees of automation and lean cross functional teams.
• Re-architecting for the cloud: Though lift and shift can be a great way to get started in securing the benefits of
cloud, the transformative benefits come when we rearchitect and take advantage of cloud native capabilities.
• Our Dual Delivery & Upskilling Approach: The Contino delivery delivery model is designed to help you both
deliver and learn. Whilst helping you deliver on your most strategic Amazon Web Services projects, we will help
you to train and upskill your people so that knowledge and skills are built within our organisation.

30. Accelerator:
AWS CLOUD STRATEGY
This accelerator is designed for enterprise organisations
who are looking to develop a strategy for succesfully
adopting and consuming the Amazon Web Services
public cloud.
It includes infrastructure design and solution
architecture, and development of a roadmap for how
and where to deploy AWS within their organisation.
The strategy we develop is based on our Enterprise
DevOps model which uses high degrees of automation
and small cross functional teams to build and manage
more of their own infrastructure.
Outputs:
● A documented solution architecture for infrastructure
design, environment design, networking and security.
● Advice on operational and development tooling to
support your use of your cloud.
● A roadmap for where and how to deploy AWS cloud
within your infrastructure and application portfolio.
● An upskilled workforce with a better understanding of
cloud technology.

31. Accelerator:
AWS DEVOPS CLOUD OPERATING MODEL
This accelerator is designed for enterprise organisations
who are looking to integrate Amazon Public Cloud into
their workflows and IT function, and need to update
their processes to fully take advantage of cloud.
It involves identifying key roles and responsibilities in
managing the public cloud between central IT, business
units and teams and documenting key process flows
such as change, incident and release management in a
cloud native world
This all combines to create the policies and tooling to
help your organisation and team be good citizens in the
cloud.
Outputs:
● A documented cloud operating model tailored for
AWS and DevOps approaches.
● A high level governance guide describing how the
cloud will be used in your organisation.
● An upskilled workforce with a better understanding of
cloud technology.

32. Accelerator:
AWS CLOUD READINESS ASSESSMENT
This accelerator is designed for enterprise organisations
who are ready to move application workloads from their
data center into Amazon Web Services.
We help you categorise your applications into a state of
cloud readiness based on our 10 point scale, and
highlight any risks and remediation points in succesfully
migrating these applications.
As well as looking at the application architecture, we will
more broadly look at the skills and ways of working
within specific application teams to see if they are ready
to secure the benefits of working within the cloud.
Outputs:
● Tailored application Questionnaire against each of the
applications in scope for cloud.
● A red/amber/green report of applications in scope,
classifying according to our 10 point scale.
● A remediation plan for each application in scope.
● Targeted workshops to demonstrate the primary
cloud platform opportunities.
● An upskilled workforce with a better understanding of
cloud technology.

33. Accelerator:
AWS CLOUD NATIVE APPLICATION MIGRATION
Outputs:
● A migrated application which is fit and optimised for
the cloud.
● Decommissioned application within your data center
● An upskilled workforce with a better understanding of
cloud technology
This accelerator is the fun part – actually migrating your
applications into Amazon Web Services.
Our cloud native application migration model goes
through the process of remediation, preperation, move
and cloud optimise. We may jointly take the tactical
approach to lift and shift, but our joint goal is to look for
opportunities to make our applications more cloud
native and cloud optimised.
The full migration process will be based on a DevOps
delivery model, using high degrees of automation to fully
software define your technology stack.

34. CONTINO HAVE DELIVERED AMAZON WEB
SERVICES WITH LEADING ENTERPRISE BRANDS
One Of UK’s Top 3 Largest
Retail Banks
Building AWS capability for
central IT group
Rationalising development
toolchain
Introducing More Automation
Into Delivery Pipeline
Advising On Strategy For DevOps
Transformation
One Of UK’s Top 3 Largest
Retailers
Implementing first connection
to AWS
Configuration Managing On
Demand Environments
Infrastructure As Code
Definition
Upskilling & Training Global
Engineering Workforce
One Of UK’s Top 3 Largest
Telecoms Providers
Integrating Cloud Broker With
AWS
Configuration Managing On
Demand Environments
Improving DevOps and
Continuous Delivery Pipeline and
Improving Rigour Of Software
Development Lifecycle
We are working with many of the largest enterprise brands across verticals on their AWS deployment
journeys.

35. Questions!
www.contino.io
Benjamin.Wootton@contino.io