It’s Important for success! Session Objective
18
Transcript of It’s Important for success! Session Objective
It’s Important for success!
Session Objective:
Learn what belongs in your cutover plan,
where it fits in the overall project schedule,
and gain some retrospective insights.
Easy as 1 – 2 – 3
The Devil is
in the Details!
Pete and Repeat
Retrospective
Advice Board
Customers
Vendors
RoutesWarehouses,Locations,
AislesBOMsItems
InventoryBalances
Costs(if rolling)
Open Purchase Order Lines
Open SalesOrder Lines
Open AR & AP
Open GLBalances
Chart of Accounts
TradeAgreements
Production Orders
Configuration & List of Values
StaticData
Demand Forecast
Costs(if not rolling)
DynamicData
Note: Cost can be either Static or Dynamic
InterviewSMEs
and business owners
Customers
Vendors
RoutesWarehouses,Locations,
AislesBOMsItems
InventoryBalances
Costs(if rolling)
Open Purchase Order Lines
Open SalesOrder Lines
Open AR & AP
Open GLBalances
Chart of Accounts
TradeAgreements
Production Orders
Configuration & List of Values
Data
Demand Forecast
Costs(if not rolling) Dependencies
> 1 mo
1 mo
2 wk
Prior to 1st
mo end
Wk end
3 days
1 wk
1 wk
1 wk
Wk end
Wk end
3 days
@Go Live
Last!
No new Vendors
Hold payments & collections
Manual edits
No more
entry
Hold receipts & invoices
Ship early, avoid partials
Forecast consumption
Close out old & start new manually
Run MRP
TimingBusiness
Considerations
Plan the conversion steps
Execute the cutover plan
Test the data conversion
Evaluate issues and find solutions
Cycle Cutover Plan Comments
CRP1 Document configuration and list of values dependencies
Note missing set ups and add to plan
CRP2 Add business dependencies Simulate the dependencies during testing
CRP3 Very detailed step by step documented plan
Test plan should include scenarios for using static data and executing dynamic data
CRP4 Finalized cutover plan ~ any changes should be minor
Resolve all prior issues or define manual workaround ~ don’t alter code or mapping!
CRPx Perform additional cycles if changes made are not minor
Pete and Repeat…
UAT No more changes – add manual steps for any new issues
This is the final dress rehearsal!Reference prior cycles’ resolved issues…
GoLive
Follow the plan – don’t divert! Smoke test critical functions and problem areas
CO
MP
LE
XI
TY
~M
AT
UR
IT
Y
Step by step cutover planA carefully knitted plan containing:
• detailed steps/instructions,
• defined dependencies,
• functional area responsible,
• specific resource assigned,
• planned date/time, and
• estimated time to execute.
DataDependencies
BusinessConstraints
History
OpenActivity
(Planar’s actual cutover was over 600 steps, ~120/~20% extract/load steps)
What went well… What went well…
Get an issue tracking
system for the project
(JIRA!)
What could have
been improved…
What could have
been improved…
www.axugsummit.com/session-materials
