1. Managing Product Complexity in AX Martin Drude, Trützschler | Klaus-Jürgen Voß, b4dynamics

2. #AXUGCongress16 Truetzschler’s challenges in real life and in AX How we did not succeed and how we finally did How we keep it alive Product Builder and Product Configurator What’s next? Agenda 2 2

3. TRUETZSCHLER’S CHALLENGES IN REAL LIFE AND IN AX

4. #AXUGCongress16 Trützschler Putzerei Karden Strecken family-run business since 1888 machines for Spinning mills 3000 employees worldwide Production facilities in China, India, Brazil, United States AX 2009 in Germany and China so far

5. #AXUGCongress16 Product Complexity Karden about > 8.000 BOM lines/machine in 16 BOM levels for this machine type in the last 3 years: 2882 machines delivered 1817 generated configurations (BOMs) 211 manual configurations (BOMs)

6. HOW WE DID NOT SUCCEED AND HOW WE FINALLY DID

7. #AXUGCongress16 Our 2 main headaches 1. create the product models2. explain them to the users

8. #AXUGCongress16 Product Model in AX validation rules 36 variables with 160 outcomes tools to choose from the item master logic in the code node

9. #AXUGCongress16 Selection logic in Decision Table

10. #AXUGCongress16 Easier handling in Excel

11. #AXUGCongress16 Product configuration creates new BOMs checks, if BOM is already there and re-uses existing ones creates new item configurations (item dimension size)

12. HOW WE KEEP IT ALIVE

13. #AXUGCongress16 create centrally, use locally Product Manager creates and updates Product Models export new or changed models and import to other company accounts and AX-instances Update notification „What‘s new?“

14. PRODUCT BUILDER AND PRODUCT CONFIGURATOR

15. #AXUGCongress16

17. Migration from Product Builder to Product Configurator Main statement from Microsoft:  Product Configurator is scheduled to replace Product Builder in the next major release after Dynamics AX 2012 That causes:  Companies that are using Product Builder and want to upgrade to a future release of Dynamics AX 2012 must migrate to Product Configurator

18. #AXUGCongress16 The concepts and the functionality of Product Builder and the Product Configurator are similar in many ways. Many elements of the Product Builder maybe can be converted to corresponding elements in Product Configurator. Some features in Product Builder cannot be converted directly to their counterparts in Product Configurator. One important aspect is that Product Builder can include X++ code in product models but Product Configurator doesn‘t allow that. However, there are some key differences, and partners and customers must work together to determine how to migrate product models in Product Builder to product configuration models in Product Configurator.  That is what Microsoft tells us. In the next minutes I want to give you some examples about what we have to do in this company for transferring the different parts to Product Configurator. Migration from Product Builder to Product Configurator

19. Migration from Product Builder to Product Configurator Which data can be converted? 5

20. 6

21. 7 These data can be transferred to Product Configurator.

22. Migration from Product Builder to Product Configurator Which data can be converted? 8

23. 9 These data can be transferred to Product Configurator.

24. Migration from Product Builder to Product Configurator Which data can also be converted? 10

25. Migration from Product Builder to Product Configurator Which data can be converted? 11 I‘m sure we have no chance to transfer these data automatically.

26. Migration from Product Builder to Product Configurator Which data can be converted? 12

27. Migration from Product Builder to Product Configurator Thank you very much for your attention!

28. #AXUGCongress16 Martin Drude Trützschler GmbH & Co. KG martin.drude@truetzschler.de Klaus-Jürgen Voß b4dynamics klaus-juergen.voss@b4dynamics.com Speaker contact info 28 Please complete the survey!

29. #AXUGCongress16