Leading Nordic Financial Services Group

Transcription

1 Leading Nordic Financial Services Group Project Description : : Migration from third party Data Center to HCL Data Center Migration of Applications Timelines : Start - March 2014 End - June

2 Migration Details Migration Type: Like-to-like migration arising out of the DC consolidation exercise Servers: UNIX (Solaris) 800 Servers, Wintel Servers, Linux Applications 226 COTS & 352 custom applications Non-mainframe only Middleware (MQ, WAS, WL-based environment) Databases (Oracle, Sybase, SQL, PostgreSQL, MySQL) Network Devices ,600 users for Exchange, LYNC, SharePoint Storage 5+ PB with growth and backup of 4.5PB with growth I-series 20 Power boxes Teradata 33 Appliances Desktops & Laptops 14,700 2

3 Solution Highlights : Phase 1 - Assess the Application & Environment Application Profiling - Basic information was collected regarding the service routine including the business criticality, operating system, databases, application dependencies and vendor information. Application profiling (operational dependencies & testing)-operational dependencies and information needed for planning the testing phase was collected Application Dependencies - The application dependencies was collated from the system architect. Interfaces study - Inter-application and intra-application interface information, including the source and target host names was collected Batch Jobs detailing - Details regarding all scheduled batch jobs, including the host name, scheduling details and batch dependencies was collected Assessment of the Environment and Applications (viz. Inter-dependencies, hard coded references, etc.) was done 3

4 Solution Highlights: Phase 2 - Grouping, Definition & Execution Categorized applications to infrastructure applications, basic standalone non-production applications and pure functional applications Functional applications were further categorized based on strategic importance and Value Chain analysis, into the following. Platinum, Gold, Silver applications with NO change were marked for AS-IS Migration Platinum, Gold, Silver applications with code remediation were marked for migration, after changes & testing Planning was done in multiple waves based on business criticality, interface dependencies, & cut over windows A Migration Review Board was set up to define the guidelines on migration, test strategy, POC, checklist, cutover plan Criteria definition was gated in terms of functional acceptance, performance, downtime & migration windows 4

5 Solution Highlights : Phase 3 - Environment setup, Testing & POC The environment and installation of applications was done. Testing (Unit Testing, System Testing, SIT and UAT) was completed. POC to promote a single cluster of applications to prod environment was done. The Migration Review Board was set up to define guidelines. 5

6 Solution Highlights : Phase 4: Rollout Phase Fine tuning was done for the gating criteria, based on the POC The rollout was broken down to 4 sub phases preparation, execution, decision, & go live / roll back Timelines for the migration, downtime of the business critical applications was done A factory model for migration in multiple waves was created. 6

7 Business Benefits Transition and transformation of the bank, with a view to drive future transformations was achieved. Lead Consultant was to deliver the Transition and Transformation program across HCL, the incumbent, and the bank with a focus on budgets There was a heightened focus on Application level and Financial industry value chain specific migration Minimal Disruption for critical applications during migration to the new DC architecture was ensured. Application Operations in the bank (first time in the bank s history) across mainframe and non-mainframe systems was set up Improved availability, better governance to monitor and optimize the performance of the Infrastructure and Operations team was achieved There was a reduction in costs due to global delivery, centralization, consolidation & standardization of processes into the industry standards framework 7

8 Key Learning A: Application Due Diligence/ Discovery exercise should additionally focus on infrastructure (servers, FW, switches, etc.) related technicalities, E.g.: Application configuration, including files, locations and structure Network Deployment Architecture (VLAN details) Server & application start-up & shut-down procedures along with identification of application-specific services Database & Application Integration Inter & Intra Application Interface Analysis External application interface specifications (for IP address white-listing, etc.) Deployment of applications in Hot Standby mode Authentication process and architecture, & security implementation Application Performance Monitoring Licensing requirements (used as input for transformation-license optimization) 8

9 Key Learning B: Communication Planning: Detailed implementation (migration) plans should be created in advance and discussed with all stakeholders to notify the application downtime and testing requirements (including the applications not in scope for migration) C: Value stream test cases should be designed to cover the components of the deployment architecture (interface touch points only). The objective is to validate interface functionality instead of unit functionality as migration is performed by image copying. D: Test cases should be identified to exercise latency dependencies. E: Taskforce meetings: Daily 30 minutes meetings must be conducted, and must involve customer SPOCs and incumbent vendors to fast-track the issue resolutions. All parties must be committed to complete the migration according to the plan. 9