Cutover Planning (Templates) - DoD · XLS file · Web view ·...

EI ToolkitDocument version 1.0, June 2002Last validated: June 2004

1 of 13

Cutover Planning (Templates)

Note: Most leading software vendors and systems integrators include similar concepts and tools in their methodologies.If that is the case for your program, utilize this these spreadsheets (created from a combination of software vendor's methodologies) as a checklist or guide to ensure that your cutover process is complete.

Use this list of tasks to validate that your cutover plan is complete. Your system integrator should plan a key role in creating a cutover plan for your specific project.

Cutover Planowner:start date:end date:

Task Owner Dependency Status Signoff Others involvedGetting started1) Prepare for Cutover

Finalize cutover plan and checklistsCommunicate plan to cutover team

Plan and perform physical inventory

Implement configuration management plan2) Prepare Production Environment

Install production servers

Connect the servers to the networkCreate user accounts on the servers

Configure the file system on the serversConfigure printer drivers

Install the application servers

Duration in hours

Planned Start Date

Planned End Date

Communicate cutover timeline to the organizationCommunicate go-live timeline to customers and vendors as appropriate

Install the operation system and networking software

Install the user machines and connect them to the networkInstall the database on the database servers

Configure the standard applications database objects


2 of 13

Task Owner Dependency Status Signoff Others involvedDuration in hours

Planned Start Date

Planned End Date

Create the custom database objectsInstall the system management tools

Install printers and other peripheral devices

3) Prepare User Learning EnvironmentSee EUT Plan for details

4) Set Up Applications

Set up and compile the key flexfieldsEnter the application setupsLoad the initial setup dataImplement the security configurationRegister the application objects

Setup and compile the descriptive flexfieldsEnter or load custom seed data

Verify batch operation of the operationsBack up the production system

5) Install Conversion Programs

6) Finalize System AdministrationEnsure backups are running correctlyEnsure daily procedures in place

Ensure db has been allocated sufficiently7) Define Cutover Contingency Plan

Define contingency strategyDetermine contingency support staffDetermine contingency project team

Secure access to the production environment

Set up the application users in the new system

Verify the online operation of the applications

Install conversion programs and automated conversion tool software (if used)List the location of each conversion program in the production environmentList the location of any conversion tools in the production environment


3 of 13


Planned Start Date

Planned End Date

Define users/management procedures8) Implement Production Support Infrastructure

See Help Desk Plan for details9) Conduct User Learning Events

See Help Desk Plan for details10) Perform Acceptance Test

Validate the acceptance test environmentExecute the acceptance test scriptDocument the results

Final Cutover1) System and Network administration

Verify Printing/Faxing is working

Ensure external access to system available

2) Convert and Verify Data

Review responsibilities for the acceptance test with the teamBack up the production environment for later availability

Determine required actions for problem resolution

Make recommendations for application changes or corrections based on acceptance testingSecure acceptance of acceptance test results

Shut down legacy systems at appropriate time

Verify user Printing/Faxing defaults are set upEnsure all network communications are in place

Ensure remote printers/services are available

Verify legacy pre-conversion data cleanup has been completed


4 of 13


Planned Start Date

Planned End Date

Describe the data conversion sequenceSequence download programs

Sequence upload programsSequence translation programs

Sequence interface/validation programs

3) Verify Production Readiness

Conduct production readiness verificationConfirm the production cutoverPrepare the support team

Verify that users are trained

Distribute the initial production schedule

Obtain approval for beginning production

Sequence of interface table creation programs

Run the conversions (see Cutover Conversion Plan)Enter manual conversions (see CutoverConversion Plan)Verify the converted data (see Cutover Conversion Plan)

Secure acceptance that the converted and verified data meets century date compliance standards.

Review the production readiness verification checklist

Obtain agreement for the initial production schedule

Verify commitment and readiness of internal and external support personnelVerify the completion of the production environment

Confirm senior management commitment via the steering committee


5 of 13


Planned Start Date

Planned End Date

4) Begin ProductionInitiate using the production system

Initiate support

Declare the new system live

EITK 0604

Initiate incident/technical issue management proceduresInitiate open issues and create a resolution list

Confirm that all components of the production system are operational

05/06/2023 18:47:42 document.xls 6 of 13

Cutover Conversion Plan

The Cutover Conversion Plan should be created in detail by the technical leads.This plan will include owners and signoffs responsible for both conversions and verificationas well as what conversions are required, their type, during and sequence.

Use this list of tasks to step you through the converstion process. External consultants should assist in refining it for your specific project.

Conversion Tech Owner Process Owner Duration Start Time Finish Time Tested Signoff

05/06/2023 18:47:42 document.xls 7 of 13


Use this checklist/signoff as a final verification that you are ready to go live. Owners should be the lead for that area.

Final Cutover Checklist Owner Signoff Date

Process Acceptance CompleteGL

Integration Testing complete PROJECT MANAGERS TO REVIEW AND CONFIRMEnd user training complete THIS CHECKLIST. IT WILL THEN BE DUPLICATED FORProcedures documents complete EACH AREA.Documentation distributedEquipment readyUser accounts verifiedConversions verifiedManual conversions completeCommunications establishedFinal system test acceptedHelp desk established Final signoffLegacy systems and input stoppedFinal signoff

ARIntegration Testing completeEnd user training completeProcedures documents completeDocumentation distributedEquipment readyUser accounts verifiedConversions verifiedManual conversions completeCommunications establishedFinal system test acceptedHelp desk establishedLegacy systems and input stoppedFinal signoff

AR Order FulfillmentIntegration Testing completeEnd user training complete

· Final user acceptance· Shutdown complete· Conversion verification· Equipment verification· Communications set up · Technical verification

C9

Update the list of process/application areas being implemented

05/06/2023 18:47:42 document.xls 8 of 13

Procedures documents completeDocumentation distributedEquipment readyUser accounts verifiedConversions verifiedManual conversions completeCommunications establishedFinal system test acceptedHelp desk establishedLegacy systems and input stoppedFinal signoff

Contract ManagementFunds ManagementInventory ManagementFormula ManagementQuality Management THIS SECTION TO BE COMPLETEDProduction / POC SIMILAR TO THOSE ABOVE ONCE ALLCost STEPS FOR EACH AREA ARE CONFIRMED BY PMsOrder FulfillmentMRP / MPSBudgetsAccounts PayablePurchasingFixed AssetsInventory Management / StoresGrantsAR (Grants & Endowment)Projects (CPS)

Business Shutdown CompleteShipments THIS SECTION TO BE COMPLETEDA/P payments FROM DETAILS PROVIDED BY EACH AREAA/R cash applied ON THE CUTOVER PLANNING WORKSHEETProduction/ Inventory Reportedetcetcetc

Data Conversion see Cutover Conversion Plan for detail

Equipment Set UpSystem installedSystem set upPrinters / faxes operational

05/06/2023 18:47:42 document.xls 9 of 13

CommunicationsTeam members informed of Go / No-Go decisionTeam members ready to GOHelp desk functioningIssue tracking operationalSoftware vendor hot line aware of Go Live

TechnicalSufficient disk spaceSufficient memoryProduction system verifiedLegacy systems secured or shut off

Management signoffSI Project ManagementClient Project ManagerClient Program ManagerABC SponsorsABC SponsorsABC SponsorsABC Sponsors

05/06/2023 18:47:42 document.xls 10 of 13

Final signoff

· Final user acceptance· Shutdown complete· Conversion verification· Equipment verification· Communications set up · Technical verification

05/06/2023 18:47:42 document.xls 11 of 13

Complete information for distribution and reference during cutover.Insert rows for all functional/process areas in place of 'XX' place holder.

Cutover Team and Contact Information

Role FunctionProgram Manager - Provides management support - decisions, resources, directionProject Manager - Organizes detailed transitionCutover Owner - Leads the execution of the cutover planMigration Team Member - Execute the detailed tasksTechnical Team Member - Implement production environment and performs data conversionsValidation Team Member - Responsible for final validation of prod'n environment just before go live

Role Name Hours Phone # Email Beeper # LocationProgram ManagerProject ManagerCutover OwnerGL Migration TeamGL Validation TeamGL Technical TeamAR Migration TeamAR Validation TeamAR Technical TeamXX Migration TeamXX Validation TeamXX Technical TeamTechnical Team MemberTechnical Team Member

Others:

Role Name Hours Phone # Email Beeper # LocationExecutiveProject SponsorProject SponsorProject SponsorProject SponsorHR ManagerEUT OwnerHelp Desk Owner (see also HD contacts)

A15

List all cutover team members

B15

Indicate the Cutover lead, team lead or power user responsible for each area

C15

Indicate the hours the individual is scheduled to work. If a team member’s hour vary, insert additional lines and include the day or date with the relevant hours.

D15

Indicate the phone number to be used during the specified hours.

E15

Indicate the email address to be used during the specified hours.

F15

Indicate the beeper number to be used during the specified hours.

G15

Indicate the location the team member can be found for the hours specified.

05/06/2023 18:47:42 document.xls 12 of 13

05/06/2023 18:47:42 document.xls 13 of 13


Use this log as a sample of those components that should be tracked for issues that arise during cutover of tasks to step you through the converstion process. Many projects utilize the samelog or database used during the other phases of the project. Whether a formal database is in place or not, use this as a guide to assure your issue tracking meets the typical requirements.

Cutover Issue Log

Issue # Initiator Summary Description Type Owner Resolution 12345

….

Date Opened

Impact/ Importance

Target Completion

DateCurrent Status

Completion Date

A10

sequential numbering of issues as they are logged works best

B10

name of the initiator and their contact number

C10

date and time stamp when the question or issue was raised (not the date it was logged in case there was a delay in logging it)

D10

describe the question or issue in enough detail for others referencing the log to understand it

E10

select prioritization of the issue based on its impact and importance: low – issue that needs to be addressed but does not impact going live or the timeline to complete the cutover tasks medium – does not prevent going live, but a work around may be needed and the cutover timeline may be impacted, therefore address promptly high – critical issue impacting both cutover and ability to go live, address immediately

F10

select the nature of the issue from the list defined. Edit the list via Data --> Validation from the toolbar.

G10

assign individual who is responsible for taking the next step to resolve the issue

H10

date that resolution is targeted to be completed

I10

indicates standing of the issue overall (not from the individual’s responsibility perspective)

J10

when current status is updated to ‘closed’ indicate the date that it was resolved, documented and communicated

K10

when current status is updated to ‘closed’ document the resolution defined

Cutover Planning (Templates) - DoD · XLS file · Web view ·...

Documents

Transcript of Cutover Planning (Templates) - DoD · XLS file · Web view ·...