1. Dynamics AX
Henrik Hasselblad Business Unit Manager

2. European presence Approximately 1,900 employees
Sweden
Germany 290
Norway 105
Other countries* 90
*) Other countries are Finland and UK.
Finland
Sweden
Sweden
Norway UK
Germany 2
Passion for improvements

3. Möjligheter i Det nya arbetslivet
Microsoft Acando
Möjligheter i Det nya arbetslivet
Top 5%
Global Partner 90
Customers
100 Consultants 60
Countries
60 Application Management Customers

4. A few of our Dynamics customers in Sweden
Några av våra drygt 100 talet fina Dynamics kunder, vilka några är här idag. Kul att ni kunde komma

5. Analysis / Requirements
ERP (AX) Implementation Lifecycle
BD / Pre Sales
PMO
Analysis / Requirements
Design
Development
Test / UAT
Deploy
Maintain
Phase
Lifecycle
Sales/BD
Business Analyst
AX Solution Architect
Developer
Project Manager
Staff

6. How to revert to standard?
Lead consultant presents standard functionality
Super users from all countries
If you disagree – escalate to CAB
Time box
- 50% video – 50% facetoface

7. 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)

8. What differs an upgrade from a re-implementation?

10. Upgrade - Hybrid Historical data required Unique Modifications
We always advise the customer to perform a gap/fit analyse to minimize the customization level and increase future ROI
Unique Modifications
Time & Budget 10

11. 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 11

12. Reimplement
If you have an inheritance of massive customizations or data consistancy errors
Only “need to have” data
Focus on migration
Change & Business Process Management 12

13. Pro´s Con´s Revert to standard Step by step golive
Need to have data and code
Con´s
Time consuming
Risk of missing customizations
Scope creep

14. How to approach the upgrade
Build your business case and involve top level management!
Business Process
Sure Step
Document your processes
Skill transfer by partner
Customer source
Technical
Find out your customization level
Budget for infrastructure
Skill transfer by partner
Customer source 14

15. Key Considerations for Upgrade Planning
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 AX2012
Hardware & Database Server Review and optimization
Customization complexity
Test & User Training on AX 2012
Automation with workflow
Project Management: Having a plan in place will help ensure the project is always on the right track
Execute
Test
Plan
Målet är att klara det på en helg – SN tog en dryg helg med stängd måndag, bättre hårdvara (Virtualisering NO NO)
Data Cleanup – Vid uppgradering finns det möjligheter till rensning och arkivering
Se över och mordernisera din hårdvara – byte av SQL
Application Consultant går igenom en GAP/FIT
Utvecklaren skapar en detalj analys av koden där anpassade object klassificeras I small/medium/large – Egna modeler som bygger på 20 års erfarenhet – ibland samma som LCS och ibland långt ifrån… Ett hantverk!
Runt 70 uppgraderingar på Dynamics AX
Training -

16. Key Considerations for Upgrade Planning
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 AX2012
Study new AX2012 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 AX2012
ORGMODEL
SHARED DATA:
- DB upg är mer omfattande då det är en ny databas modell
Delade tabeller I tidigare versioner är riskfaktor
VAR NOGA PRE-ANALYZE och rätta upp ALLA fel och varningar
Produkt begreppet
I särklass största problemet kring upg är en undermålig analys
Man vill inte lägga pengar på det och det är jobbigt
Börja med datatyperna,: Base ENUMS är som fastatabeller, ibland trycker MS in ett ID som redan är anvnt som anpassning, det finns inte serier avsatta
Erfarna utvecklare som kan uppgradera på rätt sätt

17. Key Considerations for Upgrade Planning
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 AX2012
Customizing out-of-the box Data Upgrade scripts to account for customizations in AX4/AX2009
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
FINNS ISV:Er
Vi jobbar efter surestep

18. Key Considerations for Upgrade Planning
Build Plan & Scope
Analyze
Execute
Test
Train
Follow the Best Practices Guidelines for each stage of the upgrade process
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 and analyze them for long running queries, table scans, etc.
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
dynamics-ax-2012.aspx

19. Key Considerations for Upgrade Planning
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 Ax2012 and test Code Upgrade
Identify your key business processes/scenarios that must be supported by your AX2012 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

20. Key Considerations for Upgrade Planning
Build Plan & Scope
Analyze
Execute
Test
Train
Train the trainer (super users)
Task recorder to produce material
Online training on customer source