1. <CUSTOMER> discovery and Transition.
Sungard AS Consulting.
6TH of May <CUSTOMER>

2. Discovery and Analysis
What:
Utilise Sungard AS discovery tooling.
Review customer documentation.
Conduct Customer interviews and Workshops
Playback findings to the customer.
Make updates & changes as appropriate.
Discovery &
Analysis
Validate
Findings
Output used as the
basis to develop
migration plan.
Why:
Understand Service dependencies, scale, criticality.
Identify candidates for Cloud adoption.
Identify components where remediation would be required.
Ensure there is a thorough understanding of the customers environment.
© 2014 Sungard Availability Services, all rights reserved

3. Migration Planning What: Why:
Identify candidates using D&A findings grouped by Service.
Asses the impact of migrating the service.
Identify suitable migration windows.
Identify candidates for a pilot migration and execute.
Carry out final validation of migration candidate servers.
Develop a “Passport” for each server in the migration event to detail per server migration activities.
Document the servers to migrate.
Document the timeline of the migration event.
Document the appropriate stakeholders.
Implement a change freeze (2 weeks prior)
Group candidate migration workloads by Service.
Execute Pilot migration event.
Develop migration plan and
workload migration activities.
Develop and publish Communications Pack
Why:
Ensure a consistent understanding and agreement of what is to move and when.
Ensure the contact details of stakeholders are up to date.
Ensure the key milestones and communication points are agreed and understood.
Move “services” to avoid components communicating over potentially low latency links.
Ensure migrations are scheduled to minimise potential service impact.
Plan and execute a pilot migration event to validate assumptions.
Confirm that the profile of migrating servers is still valid.
Using per server passports ensures consistent re-configuration of migrating workloads to adhere to Sungard standards.
© 2014 Sungard Availability Services, all rights reserved

4. Migration Execution What: Why:
Operations promote workloads to ECS.
Operations carry out OAT to ensure service components are available.
Operations confirm successful testing with migration team.
Migration team advise stakeholders of successful completion.
Customer testing begins.
What:
Remove “legacy” virtual adapters, management software etc.
Apply virtual adapters & management software consistent with Sungards support processes.
Carry out functional testing.
Sanitised workloads passed to Sungard operations for promotion to ECS.
Commence migration of workloads to Sungards OBG as per timeline outlined in the Communications pack.
Communicate progress as per milestones detailed in communications pack.
Commence migration to On Boarding Gateway.
Sanitise workloads for production readiness.
Promote to Production & hand over to customer.
Why:
Ensure “obvious” issues are resolved prior to commencement of customer testing.
Communicating via Migration team ensures consistent channel of communications.
Execution of service migration following a published timeline promotes consistent, timely decision making.
Subsequent communication throughout the event gives stakeholders confidence.
Ensure workloads are in a supportable state for Sungard’s infrastructure.
© 2014 Sungard Availability Services, all rights reserved

5. On-Boarding Gateway Approach.
1. Migration Planning.
Workloads prioritised for migration based on D&A findings.
“Passports” for each workload produced containing:
Details of workload.
Configuration activities to prepare for promotion to production.
Communications Pack produced and circulated to ensure agreement and consistent understanding of:
Workloads to be migrated.
Timeline of migration event .
Migration event contacts.
Workload D&A findings validated.
2. Migration to OBG and promotion to Production.
Hosting Location
Sungard OBG
Migration Tooling employed to move workloads to OBG
Virtualised/Physical
Infrastructure
Virtualised
Infrastructure
Passports executed my migration team.
Workloads passed to Operations.
Sungard ECS
System testing and remediation activities undertaken by Sungard Operations.
Migration team advised upon successful acceptance testing.
Migration team notify customer of successful promotion to ECS.
Customer testing begins.
Virtualised
Infrastructure

6. Approach to migration discovery
The factors considered during the migration discovery process:
What’s
Active
Is there anything unexpected?
Sungard or Customer Discovery Process
Configuration
H/w. S/w, Databases?
Dependencies
If you consolidate a Data Warehouse for example, what other systems
may be impacted/broken? Rogue SQL statements, injection scripts etc.?
Workload
How busy are the systems? Migrate busy systems first or last?
Cost
Which systems cost the most to run?
Project and Transition Team
Benefit
Can you increase revenue by moving systems earlier?
Security/Trust
What remediation is required prior to consolidation?
Application Classification
What about system criticality?
Decision Hierarchy

7. Discover and Analysis process.
Discovery and Analysis uses a number of data sources in order to provide a complete understanding:
Server Inventory
Service Inventory
Application Inventory
Interdependency Report
Application tool discovery
Tool Reports
Schedule
DC Status Reports
Tooling Rationalized data
Passports
Data Collection Plan
Migration Approach
Capacity
Planner
Migration Planning Inventory
Test Approach
Migration Event
Customer High Level / Low Level Designs
Data Validation
Tooling
Interviews
Data Changes

8. Migration Risk Assessment
The risk of migrating each service is assessed based on the D&A findings, customer interviews and requirements.
Server Level
Level 1
Level 2
Level 3 1 2 3
Level 1 4 5 6
Application Risk
Level 2
Category 9 is the highest migration risk 7 8 9
Level 3

9. Migration Event Bundling Overview
Identify applications and their associated infrastructure.
Group bundles into Migration Events. Migration Events may have one or many bundles.
Identify application interactions and determine what applications must move together to minimise risk to business operations.
Group applications that share infrastructure into Interdependency Bundles.
Group applications with critical dependencies into Dependency Bundles

10. Migration Pre-Requisites
Discovery and Analysis Data – Understand the in scope estate:
Using Sungard discovery tooling and customer discovery tooling.
Customer interviews and workshops.
Review of customer documentation.
Identify those workloads which are migration candidates and those requiring remediation.
Dependencies - Using the D&A process, Identify System/Service inter-dependencies:
Group workloads into “Services”.
Identify other dependencies such as business initiatives.
Requirements – Clear understanding of customer requirements:
Understand SLA’s, Criticality, migration windows etc.
Agreed between Customer and Sungard.

11. Migration Planning
Migration Validation – Validate understanding of migration candidates:
Check current state/configuration against D&A findings.
Findings subsequently agreed with the Customer.
Testing – Pilot a migration event to validate migration predictions:
Migrate identified pilot candidates to validate process.
Communication – Agree migration event activities and publicise:
Migration schedule agreed based on service priority, D&A findings & estimates of migration durations.
Communication agreed between customer and Sungard.
Communications Pack published detailing migration event activities.
Change Freeze - Candidates and schedule agreed two weeks prior to migration event:
Candidates may be removed, but not added or changed during the change freeze period.

12. Thank You
To learn more visit or call us on +44 (0)