1 / 32

Microsoft Dynamics AX 2009 Eldar H brekke Produktsjef, Microsoft Dynamics AX og NAV

tudor
Download Presentation

Microsoft Dynamics AX 2009 Eldar H brekke Produktsjef, Microsoft Dynamics AX og NAV

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


    1. Velkommen (noter noen stikkord her)Velkommen (noter noen stikkord her)

    2. Dynamics tar markedsandeler

    3. Dynamics og ROI

    4. Microsoft Dynamics AX Roadmap AX 4.0 Global expansion – we’ve increased the # localization to 36 and # languages support to 40, where we’ve added support for important geographies like China, Brazil and Japan Improved scalability – when we came out with AX 4.0 in June 2006, we had increased the scalability to 1,000 concurrent users, however during the live time of AX 4.0 we kept up our effort on scalability and with the release of SP2 we are able to clam 1,500 concurrent users in a single instance with a considerable load. Adaptable & Compete – [added support for web service integration, added numerous features] RTM dates: 4.0 = June 2006 4.0 SP1 = Dec 2006 4.0 SP2 = July 2007 A release cycle of a major release every 2 yearsAX 4.0 Global expansion – we’ve increased the # localization to 36 and # languages support to 40, where we’ve added support for important geographies like China, Brazil and Japan Improved scalability – when we came out with AX 4.0 in June 2006, we had increased the scalability to 1,000 concurrent users, however during the live time of AX 4.0 we kept up our effort on scalability and with the release of SP2 we are able to clam 1,500 concurrent users in a single instance with a considerable load. Adaptable & Compete – [added support for web service integration, added numerous features] RTM dates: 4.0 = June 2006 4.0 SP1 = Dec 2006 4.0 SP2 = July 2007 A release cycle of a major release every 2 years

    5. Breakthrough Innovation Detesign Themes

    6. Brukeropplevelse

    7. Bygge programvare som er elsket av brukerne

    8. Rollebasert

    9. Rollesenter

    10. List Pages

    11. Microsoft Dynamics for alle

    12. Ulike klienter – ulike grensesnitt

    13. Business Intelligence

    14. Microsoft Business Intelligence Integrerte verktřy er nřdvendig for ĺ bevege seg videre utover tradisjonell BI

    15. [Technical ‘stack’ discussion option] Microsoft Dynamic’s ‘Connected’ strategy for delivering widespread access to relevant and timely data is supported by our embrace of, and integration across, the Microsoft Business Intelligence ‘stack’. Let’s start at the base of the diagram. Microsoft Dynamics is the front end where much of the data is entered (with some coming from other systems and sources which can then be imported using SQL Server Integration Services). Data is then stored in the backend as part of the BI platform of the SQL Server Database. Reporting Services and Analysis Services (cubes) are created and utilized by Dynamics to enable insight right away. From the start, with a sound platform, reporting and analysis, Microsoft Dynamics and the BI ‘stack’ offer strength of foundation and immediate ways to gain insight. Next, as an organization grows, you need to share more information with your people. This is where the Application Layer, User Tools and Performance Mgmt applications come into play. Microsoft Dynamics, the application layer, is itself a part of the BI stack from the perspective that users access information from within their ERP and CRM system as they work. This is BI too. Then, if additional individuals need to use the data, Excel is an easy to use front end for quick analysis. And for monitoring, deeper analysis and planning capabilities, we work with PerformancePoint Server, with cubes and wizards to make insight a natural part of the way that people work with information. Finally, moving into the top level of the stack, we reach Access and Delivery options, which support those organizations who require wider distribution and access to information companywide. Using SharePoint as the basis for Microsoft Dynamics portals, we allow users to push and pull information when it is convenient for them, offering timely access, as well as creating Role Tailored home pages for relevant information access. From data entry, to information retrieval and decision making, Microsoft Dynamics works like and with these Microsoft Business Intelligence solutions, creating an end to end connected insight experience. [Technical ‘stack’ discussion option] Microsoft Dynamic’s ‘Connected’ strategy for delivering widespread access to relevant and timely data is supported by our embrace of, and integration across, the Microsoft Business Intelligence ‘stack’. Let’s start at the base of the diagram. Microsoft Dynamics is the front end where much of the data is entered (with some coming from other systems and sources which can then be imported using SQL Server Integration Services). Data is then stored in the backend as part of the BI platform of the SQL Server Database. Reporting Services and Analysis Services (cubes) are created and utilized by Dynamics to enable insight right away. From the start, with a sound platform, reporting and analysis, Microsoft Dynamics and the BI ‘stack’ offer strength of foundation and immediate ways to gain insight. Next, as an organization grows, you need to share more information with your people. This is where the Application Layer, User Tools and Performance Mgmt applications come into play. Microsoft Dynamics, the application layer, is itself a part of the BI stack from the perspective that users access information from within their ERP and CRM system as they work. This is BI too. Then, if additional individuals need to use the data, Excel is an easy to use front end for quick analysis. And for monitoring, deeper analysis and planning capabilities, we work with PerformancePoint Server, with cubes and wizards to make insight a natural part of the way that people work with information. Finally, moving into the top level of the stack, we reach Access and Delivery options, which support those organizations who require wider distribution and access to information companywide. Using SharePoint as the basis for Microsoft Dynamics portals, we allow users to push and pull information when it is convenient for them, offering timely access, as well as creating Role Tailored home pages for relevant information access. From data entry, to information retrieval and decision making, Microsoft Dynamics works like and with these Microsoft Business Intelligence solutions, creating an end to end connected insight experience.

    16. Ny funksjonalitet

    17. Modulsammensetning

    18. Microsoft Bransjelřsninger What to Say: As you know, A key product strategy for Microsoft Dynamics is to provide industry enabling features as part of the core product and have independent software vendors and partners build vertically relevant solutions on top of the core product. As with all Dynamics products, five industries have been selected as key markets to be addressed with Dynamics AX 2009 – Manufacturing, Distribution, Retail, Public Sector and Professional Services. This slide highlights the current Microsoft Dynamics AX Industry Solutions. We’ve digressed from our green/yellow/red light metaphors .. Here it is the verticals in yellow where there is a current industry solution available. As you can see, there are vertical solutions available today in the Manufacturing, Distribution, Retail, and Professional Services industries where AX 2009 offers a superior value proposition to prospects today. Industry Solutions, unchanged, are ….. Transition: So to summarize what we have learned so far about the target Microsoft Dynamics AX 2009 customer … What to Say: As you know, A key product strategy for Microsoft Dynamics is to provide industry enabling features as part of the core product and have independent software vendors and partners build vertically relevant solutions on top of the core product. As with all Dynamics products, five industries have been selected as key markets to be addressed with Dynamics AX 2009 – Manufacturing, Distribution, Retail, Public Sector and Professional Services. This slide highlights the current Microsoft Dynamics AX Industry Solutions. We’ve digressed from our green/yellow/red light metaphors .. Here it is the verticals in yellow where there is a current industry solution available. As you can see, there are vertical solutions available today in the Manufacturing, Distribution, Retail, and Professional Services industries where AX 2009 offers a superior value proposition to prospects today. Industry Solutions, unchanged, are ….. Transition: So to summarize what we have learned so far about the target Microsoft Dynamics AX 2009 customer …

    19. Workflow What to Say: This is an example of how an expense report might flow through MS Dynamics 2009 new Expense Management module. When Ivan enters and submits and expense report, it would appear on Franks task list as a form that requires approval. When he approves it the workflow system would then interpret rules and determine if it also needs to be sent to Sue or Ann, who must approve expense reports if they are over a certain amount. This is a very simple example, but you can imagine how the workflow process can help ensure compliance with any number of business rules. Anyone from a CRM background knows that workflows have been implemented in software for a number of years – probably because sales and marketing processes aren’t as defined as financial processes. Workflows in CRM can be used to assign leads, for example, based on territory, and product interest. Essentially the ERP system becomes an intelligent resource – rather than a repository of data. Transition: Now a look at Multi Site Capabilities What to Say: This is an example of how an expense report might flow through MS Dynamics 2009 new Expense Management module. When Ivan enters and submits and expense report, it would appear on Franks task list as a form that requires approval. When he approves it the workflow system would then interpret rules and determine if it also needs to be sent to Sue or Ann, who must approve expense reports if they are over a certain amount. This is a very simple example, but you can imagine how the workflow process can help ensure compliance with any number of business rules. Anyone from a CRM background knows that workflows have been implemented in software for a number of years – probably because sales and marketing processes aren’t as defined as financial processes. Workflows in CRM can be used to assign leads, for example, based on territory, and product interest. Essentially the ERP system becomes an intelligent resource – rather than a repository of data. Transition: Now a look at Multi Site Capabilities

    20. Multi-Site Struktur What to Say: As we mentioned earlier, MS Dynamics AX 2009 also allows you to create Multiple logistic units within one AX company. This was a very large area of development for AX 2009 – and it impacts all of the Supply Chain Management modules. This enables you to sell to companies or divisions of companies that have multiple sites in different regions and time zones. This applies to many manufacturing and distribution opportunities that you have had to walk away from in the past – Ask: How many of you have lost or walked away from opportunities that Multi-site would have addressed? What were the scenarios? Continue: A site, by definition, is in a single geography and time zone. A site can have multiple warehouses and production units, but a warehouse and production unit can only be associated with one site. A warehouse, by definition, holds inventory. All sites must be in the same country. Transition: The new multi-site capabilities enable the following business scenarios and processes. What to Say: As we mentioned earlier, MS Dynamics AX 2009 also allows you to create Multiple logistic units within one AX company. This was a very large area of development for AX 2009 – and it impacts all of the Supply Chain Management modules. This enables you to sell to companies or divisions of companies that have multiple sites in different regions and time zones. This applies to many manufacturing and distribution opportunities that you have had to walk away from in the past – Ask: How many of you have lost or walked away from opportunities that Multi-site would have addressed? What were the scenarios? Continue: A site, by definition, is in a single geography and time zone. A site can have multiple warehouses and production units, but a warehouse and production unit can only be associated with one site. A warehouse, by definition, holds inventory. All sites must be in the same country. Transition: The new multi-site capabilities enable the following business scenarios and processes.

    21. SharePoint i AX 2009 - Reiseregning

    22. Unified Communications integrasjon Hver transaksjon viser rřdt/gult/grřnt lys Kan chatte/maile direkte med kollegaer eller ringe pĺ IP telefoni

    23. Skalerbarhet og ytelse

    24. Grensesprengende ytelse: Microsoft Dynamics AX 2009 pĺ SQL Server 2008

    25. Mĺlkunde basert pĺ střrrelse

    26. Bygd for internasjonale virksomheter

    27. Endring i paketering

    28. Endringer i lisensiering Fra 1. juni 2008 mĺ alle nye lisenser kjřpes pĺ AX 2009 prislisten Skal det kjřpes AX 4.0 mĺ det kjřpes Microsoft Dynamics AX 2009 og nedgradere kodebrevet Brukertilgang gjennom AIF vil styres av Client for Office E-faktura og E-giro legges inn i standard

    29. Ny paketering Microsoft Dynamics AX 2009 BRL

    30. Ny paketering Microsoft Dynamics AX 2009 BRL

    31. Product Builder

More Related