Cutover Management : Overall Approach
W10
W1 W2 W7 W8 Onwards
Assess and Recommend Establish and Run (per release)
Initiation Discovery Analysis Recommendation Establish Run and Improve
Finalize assessment Core program plan Application Cutover Capability Set up cutover Manage and drive
plan System architecture dependency analysis Roadmap management Continuous
Target operating model for
Session planners Existing cutover Cutover element organization monitoring, reporting
cutover
and block SME strategy & plan analysis Cutover methodology and Establish operation and escalation during
calendars Governance Readiness analysis release cutover approach processes for cutover cutover
Risk analysis Communication framework
Provision access to framework management Coordinate with
Team structure, role &
documents & Planned tools for Communication Establish governance multiple stakeholders
responsibilities, RACI
Systems cutover analysis Gaps in current capabilities &
framework Document on Best
Finalize deliverable Business black out recommendation
practices, lessons
templates periods or peak Governance Model
Governance Model and learn and
seasons
Procedures Drive continuous
Escalation Path, reporting
improvements
Risk and Mitigation Plan
Performance Metrics
1 TCS – Travis Perkins Confidential
Cutover Management : Day-wise cutover activities (during individual releases)
• Environment readiness /provisioning, verifications & pre-requisites required for cutover & Go Live
• Overall Readiness Criteria : Customer, Partner, Users, Business, IT (Applications, DB), Infrastructure / Operations, People, Processes,
Communication
Day -4 •
•
Start the execution of the activities as per the run book validated & confirmed by Travis Perkins
Configurations (additional), checking the interface links with the in-scope applications
• Verification of the overall Master Data uploaded in the system
• Check the integration touch points as per the overall architecture
• Check & confirm the loading sequence of the master data is as per Infor M3 requirement
Day -3
• Run the transactional data scripts for upload of the transactional data
• Travis Perkins to work in parallel for establishing the networks for printers, scanners, etc.)
• Critical Issues faced during execution & stabilization logged at common place and expedited for resolution
• Run the transactional data scripts for upload of the transactional data
Day -2
• Verification & Validation post data upload
• Travis Perkins to work in parallel for establishing the networks for printers, scanners, etc.)
• Critical Issues faced during execution & stabilization logged at common place and expedited for resolution
• Final verification by deducing reports before handover (Customers, Suppliers, Opening Balances, GL Balance tallying, open SO’s & PO’s
Day -1 •
wrt to the closing data)
Validation of the network, integrations, jobs, etc.
• Execute the business tasks i.e. costing runs, verifying the GL balances, Customer & Vendor Balances, etc.
• Go Live & Handover of the system to the Travis Perkins
Day 0 •
•
Start of hypercare support
Final transition to the support team to start the post Go Live Support
2 TCS – Travis Perkins Confidential
Case Study : Cutover Management during critical carve out engagement of Infor M3
CASE STUDY
• Highly customized environment & interfaced with disparate systems
Challenges • Only a part of the business of the single entity in North America (out of total of 11 globally) to be carved out
• High risk & less time engagement
• Small cut-over & transfer window
• Environment Cloning
• Understanding of AS - IS environment along with the interfaces (both internal & external)
• Configuration changes in the cloned environment : Linkage to Interfaces, User Configuration (if required), Parameters, business
rules, etc.
TCS Solution • Data Purging for the applications - Infor M3, LIMS, RFGen, Streamserve, Codesoft, Stratatech and Nuncat
• Understanding of Business rules and requirements analysis
• Development of purging scripts
• Testing : Unit Testing, Integration Testing, support UAT
• Cutover Period : Data Purging within cutover period. Well defined cutover approach & execution to accomplish the tough task
within 72 hours of the transfer window
Benefits & • Idea of cloning helped save time & infrastructure cost (during multiple iterations)
Value • 2 rounds of iterations helped in achieving the final carve out & transfer within the dedicated transfer window
• Functional, Technical and Test case document delivered as part of the last milestone of the project
Delivered • Immaculate Cutover strategy helped to execute the engagement in a smooth & timebound manner
3 TCS – Travis Perkins Confidential
