The document discusses the business benefits of cloud computing for banking. It outlines several key benefits including the quick launch of new banking products and services to maintain competitive advantage, the ability to easily scale infrastructure up or down to cope with growth or changes, and increased collaboration and productivity for employees. Additional benefits mentioned are faster responses to regulatory changes, continuous access to the latest security features from cloud providers, and lower overall costs.

1. Business benefits of Cloud Computing for Banking
Areas Benefits
Quick launch of banking, insurance
and financial products
Cloud computing allows quick & easy provisioning of IT environments for rolling new business functionalities,
products & services to maintain competitive advantage. Cloud computing helps to accelerate global payment
processing, KYC, Anti-money Laundering initiatives, card processes etc.
Ability to cope with growth,
seasonal peaks or even
divestments/spin-offs.
The cloud system is designed to cope with sharp increases as well as decreases in workload. This increases
the speed of response, reduces risks and operational costs. Moreover Banks only pay for what they
use/consume.
Increased collaboration, higher
productivity
Cloud services enable and increase productivity with real-time business collaboration. Banks and their
employees are able to collaborate on shared documents and retrieve critical business information from
anywhere, anytime and on any device.
Regulatory, Compliance and Market
Changes
Fast provisioning of the future platforms on Cloud provides the ability to begin the early development
and deployment of new capability to cope with market, regulatory, compliance, economic & political
changes.
Access to latest security features Cloud providers have industrialised approach when it comes to enhancing, updating/upgrading security
features, data loss prevention measures, user authentication, fraud protection, Cyber Attacks etc.
Lower Costs Allow re-purposing of the HW to run non-production environments at different times to achieve higher SID to
HW ratio.
Greener IT, Reduced Carbon
Footprint. Better Corporate Social
responsibility rating.
Cloud computing has helped organisations become greener by reducing the overall footprint of DCs and
associated energy consumption
Banks are already widely using cloud computing for non-core and non-critical uses, such as human resources, e-mail, customer analytics, customer
relationship management, and development and testing (88% of surveyed EU-based financial institutions were already using cloud based services by
June 2015).

2. Benefits of moving to Cloud
 Consolidate Applications & Infra Landscape with in-built technology refresh, monitoring tools, OS, Database Management, Middleware and other
ongoing support services.
 Raise average utilisation of underlying infrastructure to at least 90% in terms of SAPS and Storage utilized.
 Reduce DC footprint and associated power, cooling and space by 60% thereby lowering associated Carbon footprint and provisioning Greener IT
 Allow re-purposing of the HW to run any non-production environments at different times to achieve higher SID to HW ratio.
 Facilitate quick (on-demand) provisioning of temporary environments for short durations (say days to months) and quick turning-off
(decommissioning) of unwanted environments.
 Provide full flexibility of ramping-up and ramping-down in-line with business workloads with continuous capacity and service level management.
 Facilitate consumption-based billing based on actual usage/consumption on set time-frame as opposed to 'installed/unused' model.
 Provide priority access to Demos, PoVs (Point-of-Views), PoCs, PROVIDER’s Consulting, PROVIDER and PROVIDER’s Co-Innovation Lab.
 Ensures you as a customer are not locked into a particular Vendor; whereby Customer can terminate the contract without any liabilities/
liquidated damages by serving an advance notice of 6 months.
 Reduce business downtime during migration phase(s) as well as operational maintenance after Go-Live by leveraging NZDT (Near Zero Downtime)
Maintenance approach.

3. Application Transformation To Cloud (AT2C)
 Business case driven approach; application analysis will inform a financial analysis to
ensure that the timing and nature of workload migration contribute to the TCO
reduction goal
 Application driven approach; analysis of the application workload will be performed to
both minimise the risk of business impact and ensure that the correct target platform
is selected
 A quick win opportunity – fast provisioning of the future platforms provides the ability
to begin the early development and deployment of new capability
 Workload migration – where desirable existing workload running in a virtualised
environment can be assimilated to run under CSA (Cloud System Automation)
providing a low impact route to improved visibility and control of the VM’s running
within the environment

4. It is all about deciding the to-be landing zones &
treatments

6. Typical Cloud Models
Private cloud
Public cloud
Build(Mulesoft)
or
Consume
Integratedservicedelivery

7. A proven set of services
to Transform applications to
exploit cloud solutions,
deliver superior customer
experience and accelerate
business outcomes:
Advise
- Assess & Plan
Transform
- Execute & Integrate
Manage
- Optimise & Innovate
Also use Application Modernisation Services to leverage core business IP contained in legacy applications & data
Applications transformation to the cloud (AT2C)
Solution Overview
Cloud
Suitability
Analysis
Cloud
service
types
Cloud
Transformation
Strategy
Determination
Cloud Apps
Portfolio
Analysis
Portfolio Analysis and Planning
Cloud -specific workload
analysis
Risk analysis
and ROI
Architecture
IaaS PaaSSaaS
Cloud deployment
models
Public PrivateManaged
Dedicated/hosted
(retain, retire)
Suitable for cloud
Need deeper
analysis
Not suitable
for cloud
Retire
Tactical
retain
Cloud
Prequalification
Cloud application
criteria
Cloud application
barriers
Apps
Rehost/S2S
migration
Replace
Re -architect /
Re-factor
Integrate/
Re -interface
Transformation Strategy
Suitable
for SaaS
Cloud suitability mapping

8. PROVIDER will identify transformation/ journey treatments required to migrate the applications and application groupings to their future state infrastructure.
The above activities will be performed prior to May 21st. The following activities will take place post May 21st and will also consist of an increase in scope to include all locations (MDC’s and regional DC’s. Timescales for this work will be defined post May 21st.
7 possible treatments
1. Re-learn: A discovery process that captures the intellectual property investment that has been made in legacy applications over many years and enables that investment
to be preserved and carried forward through modernisation.
2. Re-factor Code optimisation to improve the run-time efficiency of an application. In the context of transformation to cloud ,make code changes to take advantage of the
cloud platform without changing the application business logic or programming language.
3. Re-host
Midrange
There are two types of re-host for midrange environments: Re-host binary and Server-to-Server (S2S) migration):
Re-host (Binary): Migration of applications to lower cost modern platforms without significantly changing the business features and functions. In the context of
transformation to cloud, this involves a lift and shift the current application to the target platform without any code changes. Re-host Binary is not performed
by AT2C.
Re-host: Server-to-Server (S2S): This modernization strategy focuses cases where target environment and servers are not 100% compatible and application
changes are necessary. Migrations typically run on a set of standardised platforms and technologies. S2S is a capability that can be offered as part of the AT2C
re-host area or as a stand-alone engagement.
4. Re-
architect
Forward engineering applications to Java J2EE or Windows .NET Agile Application Architecture to enable true enterprise agility. May consist of business rule
analysis followed by recoding the application, changing the business logic and function including use of automated language conversion tooling to translate to
JAVA or /NET.
5. Re-
interface
Re-interface applications by creating new interfaces to leverage and extend the application features and value. In the context of transformation to cloud
,service-enable applications, create web services and web interfaces to be consumed as part of the application integration architecture and consumption of the
application in the cloud.
6. Replace Provides a framework to replace existing legacy applications with standard enterprise applications, industry standard applications, or newly developed
applications. In the context of transformation to cloud ,it will consist of replacing an existing application by a SaaS offering
7. Retire Decommission legacy applications from the applications portfolio. We assess the linkage of applications to be retired and then systematically manage the
shutdown of applications so that the business is not interrupted.
As part of the assessment process we will identify which treatments are the most appropriate with the customer. The criteria developed with customer to date
has already identified the initial Retire applications and some of the Replace candidates.
Treatments for Applications transformation to the
cloud (AT2C)

9. The objective of S2S
Application transformation is to
migrate and adapt application
from a current environment to a
modern target Environment &
Architecture (Cloud) without
any functional and/or technical
changes to applications
The migration implies,
remediation, update, upgrade
and any other actions to make
the applications compatible with
their target environments.
Also use Application Modernisation Services to leverage core business IP contained in legacy applications & data
Server-to-Server (S2S) Application Transformation
Solution Overview
Cloud
Suitability
Analysis
Cloud
service
types
Cloud
Transformation
Strategy
Determination
Cloud Apps
Portfolio
Analysis
Portfolio Analysis and Planning
Cloud-specific workload
analysis
Risk analysis
and ROI
Architecture
IaaS PaaSSaaS
Cloud deployment
models
Public PrivateManaged
Dedicated/hosted
(retain, retire)
Suitable for cloud
Need deeper
analysis
Not suitable
for cloud
Retire
Tactical
retain
Cloud
Prequalification
Cloud application
criteria
Cloud application
barriers
Apps
Rehost/S2S
migration
Replace
Re-architect /
Re-factor
Integrate/
Re-interface
Transformation Strategy
Suitable
for SaaS
Cloud suitability mapping

10. A transformation technique for legacy servers
Industrialized midrange server application rehost
Server-to-Server (S2S) Application Transformation
An S2S engagement is “as-is” (no functional changes) transformation engagement that is aimed to provide an industrialized
approach to transformation of a large application portfolio from one platform to another, typically Next Generation Data Center
or Cloud.
S2S Application Transformation is an end-to-end solution for mid-range servers, which combines the
expertise of data engineering, applications and infrastructure. With a thorough identification and
assessment of a client’s current environment, applications are modified suitably so they can be moved
from one server type to another, especially target cloud platforms
An advanced transformation technique for mid-range servers
For applications that
suit the new infrastructure
For Transformations an
application is recompiled
When target environment &
servers not 100% compatible
For more than a simple
‘lift and shift’ migration

11. Target
Infrastructure
Traditional
MPC
VPC
Cloud Maps
Application
Suitability
Fit to Future
Application
Roadmaps
Fit to Future
Enterprise
Architecture
Fit to Future
Business
Strategy
Fit to Future
Business
Processes
Application
Transformation
to Cloud
Application
Lift and Shift
Ready for Cloud
Encapsulated
Application
Server
Lift and Shift
Application
O/S
Server to Server
Leave As-Is
Public
Private
Managed
Factorybased
Migration approaches

12. Workload Migration Principles
Application
Treatment Group A
Application
Treatment Group B
Application
Treatment Group C
Application Treatment
Group D
Application Treatment
Group O
Application
Treatment Group L
Where applications are
currently already virtual
(virtual to virtual),
Complexity rating
Simple/ Medium,
Proprietary software non
Bespoke.
Where applications are
currently Physical but the
future direction is Virtual
(Physical to virtual),
Complexity rating Simple/
Medium, Proprietary
software non Bespoke.
Where applications are
currently Physical and the
future direction is
Physical (Physical to
Physical), Complexity
rating Simple/ Medium,
Proprietary software non
Bespoke.
Where applications are
currently Physical or Virtual
but there are reasons why
these cannot move directly to
a cloud function (Unsupported
software Retired before
migration, Unstable platform,
Direction Lift, remediate,
shift)
Where applications are
currently not in scope.
Where there is not
enough information
about the Application
therefore more
information is required
to make an assessment.
Have operating systems
that can be supported by
the future cloud
infrastructure and
therefore, require little
remediation to migrate
them across to the
service.
Move to the target stack
is dependent on the
nature of the application
and the compatibility
with the target stack
components. Therefore,
additional due diligence
may be required with the
application provider.
Some additional
measures need to be in
place to determine
whether they stay on
physical infrastructure or
move to virtualised
environments.

13. Move to Cloud - Reduces Complexity & Associated
Infra Costs
Fact File- Global Bank

14. Focus on Agility, Creativity & Innovations

15. Consumption Based Services & Infrastructure
RUN PHASET&T/SET-UP PHASE
Dev/SBX
QA
Prod
Prod + DR+ Others
Capacity
Ramp-Up
Capacity
Ramp-Up
Capacity
Ramp-Down

16. Alternatives to internal IT create competition
Emergence of the Internal Service
Provider
Public
Cloud
SaaS Private
Cloud
IaaS PaaS Public
Cloud
Private
Cloud
SaaS
Today’s IT Reality
• LOB becoming more technology aware
• Alternatives exist in the market for
direct consumption
• Technology is viewed in terms of
service value from the user
• Users & developers want simple
• Security, compliance, availability
Service
Catalog
Dev
Platform
• Compliance
• Governance
• Competence
• Data sovereignty
• Budget constraints
• IP protection
• Culture
• Agility
• Secure data transfer
Considerations
Internal Service Provider – providing the right destination for the right
application

17. Use the right destination for the right applicationHybrid IT :
C o m m o n f o u n d a t i o n & O p e n t e c h n o l o g y
Private
Cloud
Managed Private
Cloud
Managed Virtual
Private Cloud
Public
Cloud
Centralized Management Layer
Classic IT,
Enterprise
applications
Cloud Native
applications
• Security
• Availability
• Resiliency
• Compliance
• Data
Sovereignty
• Performance
• Open
• Cost
Bridge old and new
Key Factors:

18. Definition of Migration vs. AMoD
phases
Adapt Evolve
Move and adapt the current environment to a modern target
structure & Architecture without any functional and/or technical
changes to applications.
It only includes any update, upgrade and action to make the
applications compatible with their target environment
The evolve phase concerns all modernisation activities to apply
to the applications to improve its flexibility, elasticity, business
value, cloud adoption, etc...
It usually implies functional and/or technical changes
Unless absolute necessity and only for very minor actions no functional and technical changes should be applied to the application during
the adopt mode
If it is required it should be part of the Evolve mode

19. Transformation approach
Single networking environment Current & Target environments in a single network configurationAdapt Network2
1 Deploy target environment IaaS / PaaS
Production
Pre-Production
SLA 99.9
SLA 99.5
OS and SW version
levels at n or n-1
MS Windows
Linux RedHat
Linux Suse
5
PrerequisiteMigrationapproach/Factory
Secure both Current & Target env. as one Current & Target environments in a single Security configuration3
Adapt user access Security (AD)
Adapt & simplify network Security
Repeatable Migration Process
Tools / Process
Discover
Information gathering from repositories, tools & application owner
HP AT2C tools & process - HP methodology (EDGE)
Prepare
Align Design
Verify and Validate
the current situation
Develop/Refine and
prioritise
modernisation &
transformation
Options
Develop/Refine &
Validate the Target
situation
Refine the
transformation
strategy
Refine and validate
the project scope
Design / Refine
Solution
Refine transformation
Plan
Refine switch over &
back-out plan
Confirm & authorise
DevOps framework tools & Processes
Transfer to Target
Deploy Manage
All environment &
operational situation
Validated & ready
Review / validate
back-out process
Review validate &
execute switch over
process
Handover
Operate & Support
Manage Performance
Continuous
improvement,.
etc
Existing tooling &
processes
DevOps Tooling
OO – CSA – CODAR - Jenkins - Nexus AppZero – DMA ..
HP AT2C tools & process - HP methodology (EDGE)
Provision
Migrate
Industrialised Factory process
Adapt Integrate
Provision platforms
environments on
target
Migrate production &
pre-production(s)
Verify and validate
architecture
compliancy
Test
test application to
ensure full
compliancy with
Business & User
requirements on new
architecture
Run and Validate
acceptance
Integrate for operational
Situation
(re-establish interfaces, &
all other operational
dependencies)
configuration into DevOps
tooling
Apply reversed
maintenance
Validate integration
Same iteration per instance/Application/DB migrated
Review & Validate Wave plan & Project scope4

20. This DevOps Framework comprises an integrated set of existing and Open
Source operations and development tools
OM
Repository of re-usable
Models / Templates / Cloud
Maps
EM
Architecture
XS
BSM
VPV
MonitoringConfiguration Mgmt.
uCMDBNexus
Developer Workflow
Jenkins
Service Automation
OO SA DMA
CSA
CODAR
TFS
Visual Studio
MS Workbench
SAP Dev workbench
SAP Workbench
GIT
Maven
Eclipse
Java Workbench
Compute, storage and network infrastructure
OperationsDevelopment
Optional Additions Workbench Specific
Key
DevOps Framework
SiteScope
Fortify ALM
Manage and Quality Assurance
AGM SonarPPM
ALI UFT
QC

21. Transition Environment
Both Current and Target environments must be seen as One network
Adapt Security
Target Environment
Transition
Platform
High Speed
network link
Current
DC
Non-Cloud
managed
White
White MC
Grey
Black
Target Production
SLA 99.9
White
White MC
Grey
Black
Target Pre-production
SLA 99.5
Dev. –Test - Training …
White
White MC
Grey
Black
DR - Target Production
SLA 99.9

22. Note: An application is anything with logic in it, which could very well be a DataBase with built in logic
Adapt - Waves approach
•
• Cluster:
• Should remain small enough to limit complexity and risk
• Must be technologically and functionally logically grouped
• May just affect one Business Service and/or one Application but could also affect more than one
• Ideally focus to address business service one after the other
Waves Set of Clusters or a cluster of objects
Business Service mapping
A cluster of objects can be a subset of an application, an entire application, a DB or a group of
DBs, set of services or anything that forms a logical minimum entity to group
It includes all its Production and Pre-Production instances
It is defined according to Business services and Application classification mapping, and/or cross
functionality
Map object family against a or few
business services
Application classification
Classify application according to
Technology, Criticality, Complexity & risk
The move/adopt of all applications to the target environment is done through a series of waves

23. Discover & Assess
GovernanceCustomer
contributi
on
Support for information gathering from application owner
Mngtof
change
Enterprise capacity for change analysis
Early Business Implementation & Training requirement
Change leadership mobilise
Engagement initialisation & planning
Process&ToolsTechnology
architecture
Business
Architecture
Application Assessment
When required
Collect extra application
information to complete
existing InfoBase
To highlight technical &
business aspect, &
dependencies to take into
consideration in the
migration process
Analyse Develop & refine Option Prioritise & Select
Current Situation
Analyse collected application
data
Confirm current application
situation
Highlight modernisation
opportunities
Option
Define/Refine
modernisation &
transformation options
• Vision & core
capabilities
• Technology option
• Improvement
• Target Model
Prioritise and select
options
Strategy overview
Information gathering from
repositories, tools (uCMDB,
CSA, ..) & application owner
HP AT2C tools & process
HP methodology (EDGE)
Current Situation
Model Current
Model Current
Confirm the current
application architecture
together with
dependencies (Interfaces,
MdW,..)
Continuous process feedback & improvement

24. Align
Process&ToolsTechnology
architecture
Business
Architecture
Target Architecture High Level Solution Transformation strategy Refine Business case
Develop Target Situation
Describe the Target
application architecture
Highlight
modernisation actions
HP AT2C tools & process
HP methodology (EDGE)
High level Business
requirement and
technological solution
Refine the transformation
strategy to adapt application
on target
platform/architecture
Develop Target Define transformation Plan Project
GovernanceCustomer
contributi
on
Mngtof
change
Validate and approve Transformation strategy and
transition Plan
Project plan & Process
Project Management structure Planning for next phaseProject Management structure
Business
Implementation and
Training requirement
Change Impact
Refine and validate the
project scope
Continuous process feedback & improvement

25. Design/Refine
Process&ToolsTechnology
architecture
Business
Architecture
Detailed current
situation
Detailed business &
technical
requirements
Provide details
current application
architecture
Stipulate specific
requirements and pre-
requisites needed to
conduct the
transformation from the
current to the Target
situation
HP AT2C tools & process - HP methodology (EDGE) – DevOps Processes
Detailed and review
business & technical
design
Detail Target situation
design
Review and validate
Target architecture
Test Pan
Produce/Refine Test
plan required to ensure
full compliancy with
Business and User
requirements and new
architecture
Design Solution Plan Transformation Confirm & Authorise
Transition
plan
Adapt transformation plan
to include specific tasks
and actions to include in
order to adapt the
application to target
architecture
Refine switch over & back-
out plan
GovernanceCustomer
contributi
on
Mngtof
change
Validate and approve Transformation/Transition Plan
Planning for Adapt phase
Stakeholder
communication &
Involvement design
stage
Detailed Change
Impact and readiness
assessment
MoC Effectiveness
assessment design
stage
Implementation and
training capability
design
If needed refine
business case
Existing test tooling &
processes
Continuous process feedback & improvement

26. Conduct application and/or Data/DB actions to adapt and migrate it onto Transition platform.
Adapt (application)Process&ToolsTechnology
architecture
Business
Architecture
Provision platforms on
Target
Migrate application Adapt Migrate & Adapt
Business and technology
review
Fully configured
(as per defined
specification from design
phase) transition and
target platforms must be
provisioned on target
environment
Transfer application from
current onto Transition
platform(s)
Service Automation
processes and tools CSA –
OO -
Conduct all necessary updates
and other activities to ensure
full compliancy with target
architecture
Repeat until fully compliant
When applicable recreate Pre-
production environments from
production environment using
existing process and tools.
If not execute same migration
and adapt phases as production
to all pre-production
environments
Run necessary actions
to verify and validate
architecture compliancy
Provision Migrate Demonstrate & review
Production Pre- Production
ALI/ALM - CSA – CODAR – Jenkins - Nexus - AppZero – Double-Take – PlateSpin - …
HP transformation Factory tooling & process
GovernanceCustomer
contributi
on
Mngtof
change
Project plan & Process
Validate and approve Transformation strategy and
transition Plan
Project Management structure Planning for design phaseProject Management structure
Continuous process feedback & improvement
Ongoing
Stakeholder communication &
Involvement
Ongoing
Change Implementation and
training delivery

27. Conduct application and/or Data/DB actions to adapt and migrate it onto Transition platform.
Adapt (Oracle)Process&ToolsTechnology
architecture
Business
Architecture
Provision platforms on
Target
Migrate Oracle DB and
business logic
Adapt
Fully configured
(as per defined
specification from design
phase) transition and
target platforms must be
provisioned on target
environment
Transfer Oracle DB and
business logic from current
onto Transition platform
Service Automation
processes and tools CSA –
OO -
Conduct all necessary updates
and other activities to ensure
full compliancy with target
architecture
Upgrade Oracle to required
target version level
Repeat until compliant
Provision Migrate Demonstrate & review
Production
GovernanceCustomer
contributi
on
Mngtof
change
Project plan & Process
Validate and approve Transformation strategy and
transition Plan
Project Management structure Planning for design phaseProject Management structure
Ongoing
Stakeholder communication &
Involvement
Ongoing
Change Implementation and
training delivery
Migrate & Adapt
Business and technology
review
When applicable recreate Pre-
production environments from
production environment using
existing process and tools.
If not execute same migration
and adapt phases as production
to all pre-production
environments
Run necessary actions
to verify and validate
architecture compliancy
Pre- Production
ALI/ALM - CSA – DMA – CODAR - Jenkins - Nexus ….
HP transformation Factory tooling & process
Continuous process feedback & improvement

28. Integrate into new environment: Interfaces, Processes, Tools, monitoring, etc.
IntegrateProcess&ToolsTechnology
architecture
Business
Architecture
Prepare for
operational
Situation
Implement for
operational
Situation
Prepare to Integrate
into DevOps Tooling
Integrate into
DevOps Tooling
Verify integration
ValidateDependencies
Apply reversed
maintenance
DevOps framework
Reversed
maintenance
GovernanceCustomer
contributi
on
Mngtof
change
Project plan & Process
Project Management structure Planning for test phaseProject Management structure
Development supportProcess support
Ongoing
Stakeholder communication &
Involvement
Ongoing
Change Implementation and
training delivery
Validate all actions
to re-integrate the
application/DB into
an operational
situation
Execute activities to
prepare for operational
situation
Re-establish and validate
interfaces, and all other
dependencies (network,
security, scheduling,
printing, etc..)
Validate all actions to
Integrate the
application/DB into
DevOps tooling
Configure DevOps
tooling to Integrate the
application/DB
Finalise & validate
operational Situation
Verify and validate
integration phases and
activities and prepare
for test
Apply all development
changes made to
application during all
earlier migration
processes
ALM - CSA - HP AT2C tools & process , HP
methodology (EDGE)
All DevOps framework tools and processes
“ Developer Workflow Automation, Configuration Mgt, Monitoring
Service Automation, Architecture,.. ”
HP transformation Factory tooling & process
Continuous process feedback & improvement

29. Thoroughly test application to ensure full compliancy with Business & User requirements on new
architecture
Test
Process&ToolsTechnology
architecture
Business
Architecture
Existing Test tooling & processes
DevOps Tooling & Processes
HP Test Factory tooling a process
AcceptancePrepare test
Prepare test cycle schedule
Prepare test environment
Validate environment
before running the test
Execute test
Execute test scripts,
compare results with
expected results, identify
and resolve any
discrepancies
Deliverables are the
results, fixed defects, and a
fully implemented test plan
Run acceptance test
and Validate
acceptance
AcceptanceTesting process
Closing the test
Close test
Complete test phase as
needed
Verify all exit criteria are
met and all benefits are
recorded
The expected results are
the test report
Define approach
test strategy as a starting
point
Describe objectives, scope,
input / output criteria,
tools and test environment
for testing phase
Plan tests
Identify scenarios & test
conditions
Define test cycles for entire
phases
Plan test environment
Identify and plan the test
environment needs
GovernanceCustomer
contributi
on
Mngtof
change
Validate acceptance
Project plan & Process
Project Management structure Planning for deploy phaseProject Management structure
Provide test scripts, scenario & processes , contribute to test planning, execution and validation
Ongoing
Stakeholder communication &
Involvement
Ongoing
Change Implementation and
training delivery
Continuous process feedback & improvement

30. Deploy
Process&ToolsTechnology
architecture
Business
Architecture
Business rollout
preparation
Rollout
Synchronise
target with current state
Validate Rollout process
for
production &
pre-production
environments
DevOps framework tools & Processes
Prepare Switch-Over Handover
Solution
Implemented
Execute
Switch-Over
process
Validate Solution
readiness for handover
Switch-Over review
Review and validate
entire Switch-Over &
back-out processes
Handover
Environment now into
production
Post
Implementation
Post-implementation
assessment and
review
GovernanceCustomer
contributi
on
Mngtof
change
Launch preparation
Validate and approve switch-Over
Project closed
Perform Management for implementation
Manage Continuous change
Application Development freeze period
Validate and approve handover
Management of Change effectiveness
implementation review
Finalise communication and training activities
Production
environment &
operational situation
validated & ready
Continuous process feedback & improvement
Execute Project closure

31. Manage
Process&ToolsTechnology
architecture
Business
Architecture
Live Operation services and functions
DevOps framework tools & Processes
Operate & Support Manage Performance Continuous improvement
Performance management Continuous improvement
GovernanceCustomer
contributi
on
Mngtof
change
Change leadership renew MoC Strategy & Plan Review
Stakeholder communication
and involvement manage
stage
Release and project management plans
Program management office
Release and project performance monitoring
Continuous process feedback & improvement

32. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Restricted.
Sample Wave plan

33. Adapt - Wave Strategy
Wave content selection method
• The cluster selection criteria per wave are:
1. Current technology
• To optimise migration process & resources efficiency, the Wave should address the same technological migration strategy: e.g: migrate from RedHat 5.8 and
Oracle 11.2 to RedHat 6.4 and Oracle 11.2 or Win2003 to Win2012
2. Business Services
• Focus on a specific Business Service, although clusters will likely affect other BS
3. Cluster classification
• All Clusters within the same wave should preferably contain object (Application, DB, Services,…) of similar profile : e.g. Oracle DB

34. Adapt - Wave Strategy
• The Wave execution approach is to start with a simple wave to prove &
validate the adapt process, a next wave to get the entire process into gear,
then proceed with the remaining asset
• Wave0:
• Proving wave to test, validate and improve the Adopt migration process
• Unlike other waves, group clusters of different profile to test different migration factory processes
• Wave1
• Focuses on business service and similar current technological profile (RedHat 5.8/6.4 & Oracle 11.2)
• Wave will Execute standalone
• Being in early process phase it will take longer as it gets the entire practice into gear
• Other Waves
• Waves will execute both in parallel and sequentially

35. Wave 0
Proving Wave
Provision
Target
Prepare
Migrate
Transfer to TargetSetup DevOps
Prepare DevOps Tooling
Configuration into DevOps
Tooling
Cluster 1
Provision
Target
Prepare
Migrate
Transfer to TargetSetup DevOps
Prepare DevOps Tooling
Configuration into DevOps
Tooling
Cluster 2
Provision
Target
Prepare
Migrate
Transfer to TargetSetup DevOps
Prepare DevOps Tooling
Configuration into DevOps
Tooling
Cluster 3
Provision
Target
Prepare
Migrate
Transfer to TargetSetup DevOps
Prepare DevOps Tooling
Configuration into DevOps
Tooling
Cluster 4
Continuous Adopt / Migration process review & improvement
Short cycled with low complexity and criticality clusters
Different technology profiles e.g.:
- RH5.8/Oracle 11.2 to RH6.4/Oracle 11G
- RH5.8 / Oracle10.2 to to RH6.4/Oracle 11G
- Win 2008 to Win 2012
- Win 2003 to WIn2012
Review and improve process
Prepare for
Wave 1

36. Wave 1 to #
Clusters of same technology profiles
Clusters may have mixed cycle, complexity and criticality
May apply focus on one Business Service
Review and improve process
Continuous Adopt / Migration process review & improvement
Prepare DevOps Tooling
Prepare Migrate Transfer to Target
Configuration into DevOps
Tooling
Continuous Target Provisioning
Prepare Migrate Transfer to Target
Configuration into DevOps Tooling
Prepare Migrate Transfer to Target
Configuration into DevOps
Tooling
Prepare
Prepare
Migrate Transfer to Target
Configuration into DevOps Tooling
Migrate Transfer to Target
Configuration into DevOps Tooling
Migrate Transfer to Target
Configuration into DevOps
Tooling
Migrate Transfer to Target
Configuration into DevOps Tooling
Prepare
Prepare
DevOps Ready
ETC..ETC..

37. HybridCloudDevOpsBusinessServices
Organisation
Governance
Workplace
Q1 Q2 Q3 Q4 Q5 Q6 Q7 Q8 Q9 Q10 Q11 Q12
Wave 0 - (Proving Wave) Wave 1 Central Invest ProgrammeRemaining Waves
Adapt - Wave Plan
Helion Cloud
Enablement
Adapt Network &
Security
Review &
Validate
Wave plan &
Project scope
Wave 0
(Proving Wave)
Horizontal Business Service Monitoring
End-to-end B-SLA reporting
Setup DevOps
Continuous provisioning of target environment for wave activities
Configure DevOps Tooling
End of Wave MigrationStart Wave Migration
DevOps
Operational
CC80 Monitoring
Field Agents Monitoring
Developer Workflow & Workbench
Wave 1
Configure
DevOps Tooling
Configure DevOps Tooling
Wave 2
Wave 3
Wave 4
Wave 5
Wave 6
Wave 7
Wave 8
Wave 9
Wave 10
Wave #
Wave 11
Prepare DevOps Tooling