1. Visit our Focus Rooms Evaluation of Implementation Proposals by Dynamics AX R&D Solution Architecture & Industry Experts Gain further insights on Dynamics AX Industry Solution Offerings Resolution Guidance on Solution Roadblocks Networking Focus Topic Highlight Business Intelligence Tuesday 2.15pm – 5.45pm Risso 6C Risso 8A Risso 7B Risso 7A Risso 6C Risso 6A/B

2. DISCLAIMER ©2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. Other names and brands may be claimed as the property of others. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. All pre-release product release dates and features specified are preliminary based on current expectations, and are subject to change without notice. Microsoft may make changes to specifications and product descriptions at any time, without notice. Sample code included in this presentation is made available AS IS. THE ENTIRE RISK OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS PRESENTATION. Microsoft products are not intended for use in medical, life saving, or life sustaining applications.

3. NICE,FRANCE LEARN | INSPIRE | INNOVATE TECHNICAL CONFERENCE 2011

4. IMPLEMENTING DYNAMICS AX – FUNCTIONAL SOLUTION ARCHITECTURE LACHLAN CASH SESSION CODE : BRK226 PRINCIPAL SOLUTION ARCHITECT MICROSOFT CORPORATION.

5. Today we will discuss… Your role in the changing landscape Minimizing risk, designing for consistency, managing complexity Teams, role, tools, and activities of the functional architect Functional patterns

6. Pains and challenges Sara, Charlie – Organization Management Establish and manage organization goals Alicia, Purchasing Agent – Business User Carry out tasks to meet organization goals Tim, Chris – IT Management Manage systems to support organizational goals

7. Timelines How long working with Dynamics AX or other ERP applications? Relational databases ~40 years Packaged business apps ~40 years ERP ~20–25 years Double-entry accounting ~600 years

8. Changing landscape Time

9. Changing landscape – Customer Size Time

10. Changing landscape – Complexity Time

11. Changing landscape – Implementation Time Time

12. Changing landscape – Budget Time

13. “THE ROLE OF A SOLUTION ARCHITECT IS TO SOLVE A PROBLEM BY DEFINING A SYSTEM THAT CAN BE IMPLEMENTED USING TECHNOLOGY. GOOD ARCHITECTS DEFINE SYSTEMS BY APPLYING ABSTRACT KNOWLEDGE AND PROVEN METHODS TO A SET OF TECHNOLOGIES WITH THE GOAL OF CREATING AN EXTENDIBLE AND MAINTAINABLE SOLUTION.” The Architecture Journal, Journal 15 www.ArchitectureJournal.net Domain knowledge / Ability to conceptualizeTechnical knowledge / Ability to apply patterns PROBLEM DEFINITIONSOLUTION DEVELOPMENT

14. Role of a Functional Architect So what is it you need to do?

15. Understand Components of Microsoft Dynamics AX

16. Understand the business process

17. Understand the As-Is Systems

18. Design the To-Be Systems To-Be

19. Role of a Functional Architect Diagnostic Lead or play a part of the team in the diagnostic Requirements and Process Review Proof of Concept Development Output Fit / Gap Analysis Solution Blueprint Proof Of Concept Analysis Functional Requirements Analysis ISV Analysis Output Functional Requirements Updated Solution Blueprint Updated Proof of Concept Design Systems Design Development Design Output Functional Specifications Integration Specifications Testing Plans Development Development Design Review Testing Output Design Changes Bugs Operation Roadmap for the systems Assessment of next phases of the project Output Operations Hand Over

20. Change How do you get 300 people to change what they are doing?

21. Relationship to other roles in the project FSA Project Manager Functional Architects Technical Architects Consultant/PMDeveloperTest Business Management Business Users Communication

22. Tools of the trade Diagnostic InformationSource SureStep Analysis Application Analysis Business Process Modeling Tools BPMN Value Stream Mapping Design Functional Design Template Integration Design Development Design Change (DCR)

23. Quiz How old is double-entry accounting? 600 years (give or take) So what has changed? – We still buy and sell products and services

24. What is the difference? Small Business Large Organization Economies of Scale Volume (Product, Service) People (No., Location) Economies of Scale Volume (Product, Service) People (No., Location)

25. Operations Financial and Operational Patterns Concerned with recording the financial impact of an event in the system Financial Organization – Legal entity structure Event – Date, currency, amount Documents – Journal – Invoice Financial Managing the operational activity of providing a good or service to a customer Operational Organization – Supply chain organization Event – Date, qty, transactional information Documents – Sales Order – Manufacturing Production Order

26. Operations and Financial Financial Event Financial Event Financial Event Financial Event Financial Event Financial Event Financial Event Financial Event Financial Event Financial Event

27. Technical Organization Financial Organization – Company Structure – Accounting Structure Design Operations Organization – Business Units – Supply Chain Organization Geography Organization Size Transactional Volume Functional Localization Requirements Instance Strategy Database Sizing AOS Sizing

28. Data Organization Legal Entity IE Legal Entity IE Legal Entity FR Legal Entity FR Legal Entity UK Legal Entity UK Legal Entity US Legal Entity US Global Address Book (People/ Organization) COA, Calendars, Currency, Product Other Master Data…… Administrative Data, (Users, Security……)

29. Legal Entity US Legal Entity US Global Address Book (People/ Organization) COA, Calendars, Currency, Product Other Master Data…… Administrative Data, (Users, Security……) Customer Vendor Sales Order Invoice Purchase Order Released Products Sites Warehouse Shipments Receipts

30. Technical Data Lifecycle Data Take On Master Data – Who is the owner of master data? – New Account Code introduced – Number sequence Security Auditing Functional Migration timeframe/window Parallel Systems Systems Integration Disaster Recovery Plan

31. Technical Integration Design Master Data Strategy Schema Design Frequency/Consistency Transaction Support Functional Development Options – Services –.NET Interface Disaster Recovery Plan

32. Technical Business Intelligence Financial Reporting – Consolidation Operational Reporting Functional Consolidation – Data Warehousing Financial Reporting Tools

33. Does the cloud affect the FSA? Same role, different implementation and systems

34. Similar Patterns across Industries

35. Demo : Implementing AX Technical Architecture using Solution Accelerators PersonaPain Points and ChallengesFeatures CoveredResults and Benefits Solution Architect Product knowledge deep dive InformationSource Core Concepts Learn about AX 2012 features – Deep dive Solution Architect Data take on organizationRapid Start Reduce application configuration time Solution Architect Understanding AX architecture & data model Application Analysis Tool Data model and sequence diagram visualization

36. Top Tips from the Session Understand the role of the Functional Solution Architect – Look at the big picture – Put things in context – You are part of a team – Plan for change – Understand the patterns Tools – InformationSource – SureStep – RapidStart – Diagraming Tools – MorphX – Application Analysis Tools

37. Related sessions BRK201 – Microsoft Dynamics AX 2012: Maximizing usage of the architecture on your implementations BRK225 – Implementing Microsoft Dynamics AX – Technical Solution Architecture BRK226 – Implementing Microsoft Dynamics AX Functional Solution Architecture BRK260 – Microsoft Dynamics AX RapidStart Services BRK219 – Models and the Meta Data Architecture BRK209 – The right tools for the job. Understanding the Business Intelligence Options in AX 2012 BRK224 – Performance: Benchmarks, Features and Patterns BRK222 – Deploying and Managing Security using the New Role Based Security Model BRK228 – Managing Financials with Microsoft Dynamics AX 2012 BRK242 – Microsoft Dynamics AX Financial Reporting Options including Management Reporter BRK229 – Modeling your Organization BRK230 – Building efficiency in your business with the use of the Microsoft Dynamics AX Global Address Book BRK232 – Product Information Management BRK218 – Utilizing the Workflow Infrastructure to Automate Your Business Processes & Improve Performance BRK240 – Managing the Accounts Payable Process BRK241 – Managing the Accounts Receivable Process from Invoicing to Payments to Collections BRK252 – Project Management and Accounting for Every Industry CHK224 – Solution Architecture Q&A

38. Q&A

39. Visit our Focus Rooms Evaluation of Implementation Proposals by Dynamics AX R&D Solution Architecture & Industry Experts Gain further insights on Dynamics AX Industry Solution Offerings Resolution Guidance on Solution Roadblocks Networking Focus Topic Highlight Business Intelligence Tuesday 2.15pm – 5.45pm Risso 6C Risso 8A Risso 7B Risso 7A Risso 6C Risso 6A/B

40. © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows 7 and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.