What is the Typical Upgrade Project Flow?

advertisement
Upgrading NAV & How to Ensure a
Smooth Transition to the RTC
Dynamics NAV Midwest Regional User Day
May 9, 2012
Chad Williams & Jenny Hollingsworth
ABC Computers, Inc.
Peer to Peer | Greater Scale | More Voices | Faster
www.navug.com
Where USERS Make the Difference!
Introduction
 Jenny Hollingsworth
– Application Consultant
 Chad Williams
– Development Manager
 ABC Computers
–
–
–
–
In business for about 28 years
3 locations in WI and 1 in South Bend, IN
Top Microsoft partner specializing in NAV
Over 70 customers throughout Midwest/US
Where USERS Make the Difference!
Microsoft Dynamics NAV 2013
 No more Classic Client
 Role Tailored Client Only
 Need to be using Microsoft SQL Server, not
C/SIDE database
If you want to stay current, what is the best
path to get you there?
Where USERS Make the Difference!
What Are Your Options?
 Option 1: Go directly to the NAV2009 RTC
or NAV2013
 Option 2:
– Go to NAV2009 Classic Client
– Phased approach to get to NAV2009 RTC
– Then upgrade to NAV 2013
Where USERS Make the Difference!
Why Go to NAV2009 Classic First?
 Less of a “SHOCK” to the users
 Minimizes risk, you can control how much
of RTC you start using and when
– However, do NOT let Classic client become a
crutch
 Allows you as a customer to control the
cost
 More proactive approach
Where USERS Make the Difference!
What is the Typical Upgrade Project Flow?
 Planning Process
–
–
–
–
Conduct a Procedure Survey
Understand your business processes
Identify GAPS between old and new versions
Decision: Re-Implementation or Standard Upgrade
 Development
– Compare & Merge Process
– Data Conversion
 Test Deployment
– Establish a test environment
Where USERS Make the Difference!
What is the Typical Upgrade Project Flow?
 ABC Computers Testing
– Preliminary testing to catch frontline errors
 Customer Training
– Training on any new functionality being utilized
 Customer Acceptance Testing
– Create a test plan and use it
– You know your system better than anyone
– Taking full responsibility for testing ensures success
Where USERS Make the Difference!
What is the Typical Upgrade Project Flow?
 Deployment (Go-Live)
– Scheduled during off business hours
• Typically over a weekend
– Data conversion can be done remotely
– Upgrade clients, server, and licenses
– Application Consultant onsite, Developer oncall remotely
Where USERS Make the Difference!
Next Step – Transition to RTC
 Object Transformation
– Dataports to XML ports
– Forms to Pages
– Classic Reports to RTC Reports
 Training on RTC
– Review and select User Roles
– How to Navigate in the RTC
– How to Customize in the RTC
 Phased Approach by User/Department
Where USERS Make the Difference!
Final Step – Upgrade to NAV2013
 Repeat “Typical” Upgrade Process instead
of a “Complex” Upgrade
Where USERS Make the Difference!
How to Ensure a Successful Upgrade
 Planning Upfront
– Spend the time upfront, critical step
 Communicate changes before they happen
 Use a phased approach
– Don’t do everything at once
 Take ownership of NAV
– TEST, TEST, TEST
 Review Customizations
– Don’t bring forward customizations no longer
used
Where USERS Make the Difference!
Ask the Audience
 What have you learned during an
upgrade?
 What went wrong? What went right?
 Were your goals reached?
 Questions
Where USERS Make the Difference!
Download