Dynamics AX Henrik Hasselblad Business Unit Manager Acando
Dynamics AX Henrik Hasselblad Business Unit Manager © Acando AB
Sweden Germany Norway Other countries* 1400 290 105 90 Sweden Norway *) Other countries are Finland UK. UK Germany © Acando AB Finland
Möjligheter i Det nya arbetslivet Top 5% 90 100 Global Partner Customers Consultants 60 Countries © Acando AB 60 Application Management Customers
Sales/BD Business Analyst AX Solution Architect Developer Project Manager Staff Phase BD / Pre Sales © Acando AB PMO Analysis / Requirements Design Development Test / UAT Deploy Maintain
How to revert to standard? • • Lead consultant presents standard functionality Super users from all countries If you disagree – escalate to CAB Time box © Acando AB
How can I revert to standard? • • Workshop driven Clear message from top level management Ax 2012 is master Only modify if it give you an competitive advantage Must be able to present a business case not mimic legacy Lead consultant and super users Systematic documentation (Six sigma resourses) © Acando AB
© Acando AB
© Acando AB
Historical data required Unique Modifications Time & Budget © Acando AB We always advise the customer to perform a gap/fit analyse to minimize the customization level and increase future ROI
Pro´s • • • Taking advantage of new capabilities and feature/functionality No migration of master data Less end-user training needed Con´s • Still a high customization level • Risk of skipping data cleaning • Big bang Golive © Acando AB
If you have an inheritance of massive customizations or data consistancy errors Only “need to have” data Focus on migration Change & Business Process Management © Acando AB
Pro´s • • • Revert to standard Step by step golive Need to have data and code Con´s • Time consuming • Risk of missing customizations • Scope creep © Acando AB
Build your business case and involve top level management! Business Process Technical • • Sure Step Document your processes Skill transfer by partner Customer source © Acando AB Find out your customization level Budget for infrastructure Skill transfer by partner Customer source
Build Plan & Scope Analyze Execute Test Train § BUILD PLAN and SCOPE: ‒ Some key aspects should be taken into consideration: ‒ Requirements around the downtime window ‒ Data Cleanup ‒ Purging/archiving data that is not needed in AX 2012 ‒ Hardware & Database Server Review and optimization ‒ Customization complexity ‒ Test & User Training on AX 2012 ‒ Automation with workflow Plan Test Execute ‒ Project Management: Having a plan in place will help ensure the project is always on the right track © Acando AB
Build Plan & Scope Analyze Execute Test CODE and DATA UPGRADE: ► Analyze and study your current solutions and customizations to determine which ones you intend to carry forward to AX 2012 ► Study new AX 2012 features to determine which ones can replace your existing Customizations/Solutions ► Understand the Microsoft changes that impact your upgrade Database normalization Org Model and shared data Product vs. item ► Deliver Data Dictionary (Schema) objects first: ENUMs -> EDTs -> Table -> Classes-> Forms-> Reports -> UI should be upgraded in that order ► Testing/Verification after the solutions have been migrated to AX 2012 © Acando AB
Build Plan & Scope Analyze Execute Test Train Analyze- Continued ► How much upgrade script development is required? ► Writing new Data Upgrade Scripts to migrate customizations/solutions into AX 2012 ► Customizing out-of-the box Data Upgrade scripts to account for customizations in AX 4/AX 2009 ► Consult with your VARs and ISVs to check if they have upgrade scripts in place for your upgrade project ► As the overall project makes progress, code and data upgrade can complement each other ► Upgrading Reports from your source environment can be used as a data-validation exercise © Acando AB
Build Plan & Scope Analyze Execute Test Train ► Follow the Best Practices Guidelines for each stage of the upgrade process http: //go. microsoft. com/fwlink/? Link. Id=238709 ► Plan for multiple iterations Keep a very rich, detailed log of all the findings during test iteration All iterations should be fully analyzed. Fix bugs and take that learning forward for following iterations ► Use Performance Analyzer for Dynamics Capture snapshots after each phase is performed analyze them for long running queries, table scans, etc. http: //archive. msdn. microsoft. com/Dynamics. Perf for downloading 1. 1 version is SQL 2008 only SQL 2005 version available from same link if you choose All releases link along the right side ► Check for updates to Resource Page for Upgrading to Microsoft Dynamics AX 2012 https: //community. dynamics. com/product/ax/axtechnical/b/axresources/archive/2012/02/17/resource-page-for-upgrading-to-microsoft-dynamics -ax-2012. aspx © Acando AB
Build Plan & Scope Analyze Execute Test Train ► Static Post-Upgrade Data Analysis ► Rely on Data Upgrade Test Iterations (3 -4) to bring data forward to Ax 2012 and test Code Upgrade ► Identify your key business processes/scenarios that must be supported by your AX 2012 instance. All of these tests should have a high level of data validation testing. These should become your User Acceptance Tests (UATs) and you can use them as part of user training. ► Use test cases from the initial implementation ► Perform core business processes and key scenarios on upgraded database with your data and custom code in place. ► Leverage or create a set of UATs or key business scenarios that must be supported after the upgrade in order to make a go/no-go decision © Acando AB
Build Plan & Scope Analyze ► Train the trainer (super users) ► Task recorder to produce material ► Online training on customer source © Acando AB Execute Test Train
© Acando AB
- Slides: 21