MICROSOFT DYNAMICS NAV 2016
ImplementatIon road map
INTRODUCTION
Project Preparation (As-Is) Business Blue Prints (To-Be) Realization (UAT) Migration Final Preparation Go Live (Production) Support & Maintenance
3
PROJECT PREPERATION • Requirement Discussion • Functional Requirement Document Signoff • Implementation Planning • Resource Planning • Project Charter Signoff
4
PROJECT MILESTONE Analysis & Configuration
Deliverables BRD Sign-Off, Detailed Project Plan
Design & Development
Deliverables Module Configuration, Report Customization
UAT Sign Off
Deliverables UAT Signed Off, Test Environment,
Optimize & Project Closure
Deliverables Production Deployment, Project Closure
5
BUSINESS BLUE PRINT
• Implement the Microsoft Dynamics NAV as the current system is working. • This implementation will be based on the functional (Finance, Sales and Procurements) requirement document.
6
ERP REALIZTION This phase can be concluded into phases. Base Line and Final Configuration. • User Assessment Testing • Quality Testing • Authorization Test (access control) • Enhancements reports, forms, pages and other developments • Final acceptance and correctness of the configurations
7
DATA MIGRATION • In this phase, data migration will be completed. • We will transfer all the masters (GL, Customers, Vendors, Items etc.) • We will transfer all the transactions (Sales, Purchase etc.) • Migration is the 30%/40% of implementation efforts and depend on the transaction history maintaining in the new system.
8
FINAL PREPARATION
• System Administrative Activities (Roles, responsibilities etc.) • Cut-over dates for new environment • User Training Program • Data Migration
9
GO LIVE & SUPPORT • Extend support to the end user and guiding them to check the data and reports for the requirement • Once the system stabilized, the project management prepares for the acceptance of the productive environment by the steering committee or client
10
tHanK YoU
12