1111
Centura Health Centura Health Lawson 8.x Upgrade Lawson 8.x Upgrade
ProjectProjectMarch 6, 2003March 6, 2003
Presented by: Chris L’Archevesque & Paul Presented by: Chris L’Archevesque & Paul
JensenJensen
2222
We extend the healing ministry of Christ We extend the healing ministry of Christ by caring for those who are ill and by by caring for those who are ill and by nurturing the health of the people in our nurturing the health of the people in our communitiescommunities
Centura HealthMission Statement
3333
Centura HealthLawson Environment
Prior to Upgrade
Lawson 7.2.2 applications Lawson 7.3.3 environment Lawson 7.3.3 LID UNIX S70 (12k
trans/minute) Oracle Database (50Gb) Oracle 8.1.6 AIX 4.33.8
After Upgrade
Lawson 8.0.2 applications Lawson 7.3.3 environment Lawson 7.3.3 LID UNIX P660 (56k
trans/minute) Oracle Database (100Gb) Oracle 8.1.7 AIX 4.33.10
4444
Centura HealthProject Organization
• Project Sponsor
• Steering Committee
• Project Manager
• 3 Core Teams (Finance, MM, HR/Payroll)
• Lawson Project Manager
• Lawson Consultants
5555
Centura HealthLawson 8.x Project
Timeframe• Start Date: 10/25/01
• Differences Training: 11/28/01
• Application Exploration 12/20/01
• CRP 04/19/02
• System Test #1 08/23/02
• System Test #5 11/15/02
• Lawson 8.x Upgrade 01/13/03
6666
Task Hours Start EndCyclical 4 12:00 Fri 16:00 Fri
Verification tasks 1 16:00 Fri 17:00 FriSetup 1 17:00 Fri 18:00 Fri
Prejobs 1 18:00 Fri 19:00 FriUnloads 10 19:00 Fri 05:00 SatReorgs 4 05:00 Sat 09:00 SatLoads 17 09:00 Sat 02:00 Sun
Post jobs 4 02:00 Sun 06:00 SunPost Upgrade tasks 7 06:00 Sun 13:00 SunSystem Verification 7 13:00 Sun 20:00 Sun
56
Centura HealthLawson 8.x Conversion Weekend
7777
Centura HealthLawson 8.x Lessons Learned
Planning & Organization• Leadership commitment
• Evaluate hardware upgrades
• No Such thing as too much communication
• Evaluate Risk and re-visit it on a regular basis
• Huge user commitment that needs to be agreed upon upfront
8888
Centura HealthLawson 8.x Lessons Learned
(Cont.)Testing• If you have mods, evaluate need and
get rid of them
• Make sure your scripts are robust enough to test EVERYTHING
• Upgraded data
• Hand keyed data
• Interfaced data
• Verify that EVERYTHING is tested
• If at all possible: Your testing should be done on a different box
9999
Centura HealthLawson 8.x Lessons Learned
(Cont.)Testing (Cont.)
• I.T. should perform the System Upgrade process at least 3 times
• Stay on the same UIP from beginning to end
• All 3rd party reports (i.e. ReportSmith, Crystal, MS:Access) need to be converted and tested
• If you think you are finished testing, test again
10101010
Centura HealthLawson 8.x Lessons Learned
(Cont.)Implementation• Develop a detailed Cutover document
• Task list
• Screen prints
• 2 people teams
• Develop a Back out plan and make sure it works
• Arrange for Lawson support during implementation
11111111
Centura HealthLawson 8.x Lessons Learned
(Cont.)Post-Implementation support• You will have issues, count on it!
• Depending on your environment, you should have a plan for extended support
• Application of Lawson’s CTP’s (patches) should be coordinated within the I.T. dept.
12121212
Good Luck, You are going to need it!!!
Top Related