it service transformations
DESCRIPTION
TRANSCRIPT
The smart choice for IT services and support of systems that cannot afford to fail!
Copyright © TCM Solutions Limited 2011. All Rights Reserved.
IT Service Transformations 20th July 2011
Transformation • Updates to hardware/software
• Technology – steps and leaps
• Upgrades to hardware/software
• Data centre relocation
• New technology
Make IT Better, Faster, Cheaper
Today’s Share – what’s in a word?
• Team • Business, IT, PMO, Operations all play important roles
• Clear roles and responsibilities are crucial – ‘The Buck’ stops where?
• Right skillset at the right time
• Culture • Change Leadership and Management is way of life
• Focus on continuous ROI improvement
• Goals and objectives clear
• Processes
• Repeatable Methodology
• Communications and reporting
• Measures/Outputs clear and unambiguous
Ingredients to Transformation Success
A documented and phased methodology
Planning and execution framework is flexible enough for projects of any size or complexity
Experiential – YES - but open to new ideas
Continually updated to reflect emerging risks and ways of working
It becomes YOUR methodology
Definition of Requirements Phase
Research and Data Gathering Phase
Planning Phase
Implementation Phase
Post-Implementation Phase
Transformation Methodology and Framework
• Determine and agree Scope - clear definition of requirements
• Determine overall project objective
• Identify business drivers
• Timelines and high-level milestones
• Change control
• Risk Management process
• Project reporting (reports, meetings etc.)
• Communications plan – how, what, and when to communicate Key inputs:
Business/Stakeholder/IT Requirements
Key Outputs:
Draft Project Overview Document –project bible from inception to steady state
3rd Party SOW and Commercials
Risk Register
Phase 1: Definition of Requirements
• Determine and Document Complete infrastructure NonStop platform specific
Storage (internal, ESS)
Backup (Tape Silo, VTS, Other)
Other platforms
Applications (end-to-end, dependencies, interfaces)
Network (TCP/IP, SNA, ICE etc.)
Business Requirements – co-existing
Obtain and understand existing DR Procedures
Key inputs:
Existing application/operational documentation
Workshops/Interviews with key application/platform staff
Key Outputs:
Detailed findings report
High-level Project Plan and updated Project Overview
Risk Register
Phase 2: Research and Data Gathering
• Develop & present detailed Transformation Implementation plan
• Agree timescales, responsibilities, ownership
• Determine platform transformation strategy:
Seed HW, Lift and Shift, Logical (Data/Application/Workload Switch) or combinations of above
• Logistics: Site Surveys, Security, Compliance, Communication and Notification
• Develop Test Plans/Scripts, Swing/Switch Procedures, Contingency & Backout Procedures
Key inputs:
Output from Previous Phases (Project Overview, Findings, High-level Plan)
Key Outputs:
Detailed Project Plan; ‘Move’ timeline plan(s)
Technical Solution Document
Test Plans/Scripts (infrastructure, Network, Swing/Switch, Application)
Site Plan(s)
Risk Register
Phase 3: Planning
• Team assigned and assembled
• Risk identified, assessed, mitigated and/or accepted
• Seed HW Installed and Prepared (if seed approach)
• Testing: Unit, System, Network, Application/DB build
• Platform/Application/Data Migrated
• Full user testing/commissioning
• Any new solutions implemented (if required e.g. new Tape Backup solution)
Key inputs:
Detailed Implementation Plan; Site Plan(s)
Technical Solution Document
Test Plans/Scripts
Key Outputs:
Completed Test Scripts results
System/Application/Data Migrated (‘moved’)
Service Restored/Live
Phase 4: Implementation
• Documentation Updated (DR Plans, Operational Documentation)
• ‘Parallel’ Support – Transition to Steady State
• Project Completion business acceptance
• Lessons Learned and Feedback
• Feedback and Lessons Learned Insight recombined into Methodology Framework
Key inputs:
Existing Operational procedure documentation
Key Outputs:
Updated Operational Documentation
Project completion acceptance
Lessons Learned Documented
Insight published to all stakeholders
Phase 5: Post-Implementation
What possible migration strategies can you deploy?
1. Seed Equipment • Procure/loan additional NonStop equipment and SW license to be
located in Target DC and built to mirror existing environment
• Pros
• Easy backout
• Extensive testing possible
• Allows “bedding in” time for all hardware components
• Potential for twin-tail maintenance of data
• Cons
• Cost – HW procurement and SW licensing
• Additional maintenance required (initial population vs. live)
Specific DCM NonStop Migration Strategies
2. Lift and Shift • Pre-build network and environmental requirements in Target DC then
de-install equipment and physically move to Target DC
• Pros
• Less cost
• Reduced setup and license issues
• No maintenance duplication
• Cons
• Higher Risk
• Limited testing
• Protracted outage and potentially lengthy outage required
• Extended backout/recovery
Specific DCM NonStop Migration Strategies (cont.)
3. Workload Switch / Combination • Utilise NonStop estate to transfer workload between systems (allows
individual lift and shift of each NonStop system if required)
• Pros
• Less risk than Lift and Shift – no data ‘physically’ moves!
• Full testing possible on relocated equipment
• Cons
• Existing NonStop estate may not have sufficient capacity
• “settle-in” time for relocated equipment to reduce failures
• Configuration and/or physical DC location may not allow
Specific DCM NonStop Migration Strategies (cont.)
• Planned outages Planned outages of dependent infrastructure may delay your NonStop move
• Licensing If using seed HW, don’t forget to factor in ‘temporary’ NonStop SW license costs – hp and 3rd parties
• Peripheral devices e.g. Tape Silos’ not moving – may result in new Backup Solution to be sought and implemented
• Shared Equipment E.g. ESS storage shared by NonStop and other platforms – can both move at same time?
• Business Constraints E.g. Absolutely no data loss; No Data to be physically moved – may need to look at migration from Internal to ESS storage to fulfill requirement
NonStop Migration ‘real world’ Challenges
• Software Version Currency Is Target system running same versions of OS, SPR’s and 3rd Party software levels?
• Power Requirements Does the Target DC have same power connections/requirements as source DC?
• Network Latency How far away is Target DC? Will Network performance be an issue? (e.g. DWDM Links)
• Timescales Will you incur penalties if you don’t vacate existing DC by a specific date?
• Data Centre Accessibility constraints How easy is it to get the equipment out of the existing DC? Any size, weight, or location limitations to overcome?
NonStop Migration ‘real world’ Challenges
• Understand and communicate objectives
• Follow a well-defined transformation project methodology
• Research and Data Gathering – Understand Application end-to-end and dependencies
• Plan strategy – Seed, Lift & Shift, Workload switch – determined by Risks vs. Costs / Service outage limits etc.
• Create detailed step-by-step plan, incl. resource allocation and milestones
• Implement per plan – call ‘audibles’ when necessary
• Operational Documentation Updates / ‘Parallel’ Support
• DR/BCP Procedure Plan updates / Tests
• Lessons learned – important for future projects
Summary
Questions?
About TCM Solutions
• One of Europe’s leading hp NonStop Platform Services and Healthcare Application Services companies • We’ve been providing hp NonStop Consulting and Managed Services for over 15 years • We’ve delivered hp NonStop Data Centre Transformation projects across Europe • HP certified Consultants • Customers include Financial Services, Healthcare and Enterprise Outsourcing organisations • TCM is ISO 9001 (Quality Management) and ISO 20000 (IT Service Management) certified
Further Information
Web: www.tcmsolutions.com
Contacts:
Lee Bradley Sales and Information Tel: 07850 852 512 Email: [email protected] Collin Yates Principal Consultant Tel: 07779 888773 Email: [email protected]